revert: restore some ESLint rules

[driskull]

Related Issue: #9235

Summary

• partially reverts chore(linting): restore some ESLint rules #9123. Basically, just the TSX changes where props were removed. These are all global attributes so they should be settable on any element. However, since we removed them as properties, they won't have any typings or doc associated with them which teams may think is a breaking change. So should we put these properties back and remove them at a major (breaking change) release.
• Added "@stencil-community/reserved-member-names": "warn", to eslint config because eslint was preventing commits due to these props being reserved global attributes.
• All the other eslint cleanup was kept and not reverted

[driskull]

I was wrong initially, these are all global attributes.

[driskull]

Closing, I think the maquette VDOM library just needs to update its typings to support inputMode, etc.

[benelan]

👍

The revert type should only be used when fully reverting a previous commit. Maybe we could use docs or chore instead, since that was the problem this PR resolves? For example:

chore: restore ESLint rule that removed ref for global attributes

[benelan]

Imo we should still have these documented if our components don't support all global attributes.

[driskull]

Imo we should still have these documented if our components don't support all global attributes.

Could you clarify this @benelan? What do you mean. Our components are web components which are HTML Elements. They do support all global attributes because of that nature.

[benelan]

Okay cool, I wasn't sure if all global attributes were handled correctly or not since this PR was restoring custom logic for two of them. But if all global attributes are handled correctly then we don't need to document them.