refactor: move CSS and stylesheets out of DOM

[jderochervlk]

Tracking issue: #342

Summary

• move the concrete CSSStyleDeclaration.t record out of broad DOM and into its owning module
• add StyleSheet as the owner of the stylesheet, CSS stylesheet, CSS rule, rule-list, initialization, and stylesheet operation types
• replace the prior CSSStyleSheet feature member with StyleSheet
• update dependent CSSOM, DOM, HTML, and SVG bindings to use the extracted types

Temporary state

• no compatibility module introduced by the current 16-PR stack remains after this layer
• CSS-related modules are still physically located under the broad DOM source folder, and the public feature configuration is still only the initial slice
• the follow-up Option 5 stack will establish the CSSOM folder feature, reorganize the remaining source folders, and complete the 27 public feature definitions

Review focus

• the intentional stylesheet module-ownership change
• completeness of the CSS and stylesheet extraction from DOM
• correctness of updated cross-interface references

Verification

• npm run build
• npm test
• npm run format:check

[tsnobip]

@jderochervlk what's the motivation here? Make Base feature lighter and move it to DOM feature? IMO DOM feature (not DOM.res) is already quite big in itself plus you have to take into account its feature dependencies, it's likely around 90% of the whole project right now.

[jderochervlk]

@jderochervlk what's the motivation here? Make Base feature lighter and move it to DOM feature? IMO DOM feature (not DOM.res) is already quite big in itself plus you have to take into account its feature dependencies, it's likely around 90% of the whole project right now.

I'm trying to slim down DOM.res as much as possible, you can see a larger lift in that direction on this PR: #287

DOM.res should eventually become DOM the feature, which should be lightweight. Not every project will need style sheet and CSS, so by moving this out you make using it opt in.

[jderochervlk]

@codex

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Swish!

Reviewed commit: 7f73a98ef7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".