Add _static suffixes for Uint8Array static methods

[ddbeck]

Summary

The Uint8Array static methods don't have _static suffixes, as required by the data guideline.

Test results and supporting details

This contributed to an error downstream, where the description for the web-features entry was written incorrectly. It wasn't caught because the misnaming of the keys didn't make it obvious these were, in fact, static.

See the static API data guideline.

Related issues

Via web-platform-dx/web-features#3740 and web-platform-dx/web-features#4243.

See web-platform-dx/web-features#4254 for web-features description changes related to this.

[github-actions]

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

[Elchi3]

hm, this is an API data guideline. Not a JavaScript built-ins guideline. If I see it correctly, there are zero *_static keys in javascript/ although static builtin members exist in JavaScript.

[ddbeck]

Hmm, I think it's a bit weird that they would have different notations whether they're in the JavaScript or API trees. But I see what you're saying here about the applicability. I guess to move forward on this, we'd need:

• a proposed guideline for JavaScript
• an inventory of affected keys
• a decision on whether JS and APIs should share this guideline

I'd like to know your inclinations on the last one before I fuss at all with the first two. 😅

[Elchi3]

I think we've been following the MDN content decision and in JS docs, pages get no _static suffixes in the slug, see https://github.com/orgs/mdn/discussions/264

[Elchi3]

Also, there was a question how to treat namespaces, #20114 (comment)

[ddbeck]

OK, if this is something we inherited from content, which doesn't make this distinction in URLs, then I'm fine with leaving this alone (unless and until we need otherwise, which is what I believe provoked it in APIs). I'll close this up. Thank you!