feat(jsx): add global translate attribute to HTMLAttributes

[erik-gullberg]

What is the current behavior?

Stencil's JSX typings (JSXBase.HTMLAttributes) include the standard global HTML attributes such as dir, lang, hidden, spellcheck, and draggable, but omit the global translate attribute.

As a result, <p translate="no">…</p> fails to type-check in a Stencil component, forcing consumers to work around it by spreading an untyped object.

GitHub Issue Number: #6807

What is the new behavior?

Closes #6807

Adds translate to JSXBase.HTMLAttributes so it is available on every native and custom element, consistent with the other global HTML attributes already present:

translate?: 'yes' | 'no' | (string & {});

Documentation

N/A — this mirrors the existing global HTML attributes already documented via the type definitions.

Does this introduce a breaking change?

• Yes
• No

Purely additive to an interface; existing code continues to type-check.

Testing

These JSX attribute typings are validated by TypeScript at compile time and have no dedicated runtime unit test (the same is true for the sibling global attributes like spellcheck, dir, and lang). Verified that:

• The change compiles.
• prettier --check passes for the modified file.

[johnjenkins]

let's just make this comment a bit less verbose :)

[erik-gullberg]

Thank you! @johnjenkins