fix: Register Lumo global styles before other styles

[Artur-]

Description

This ensures the styles do not override any application styles

Type of change

• Bugfix
• Feature

Checklist

• I have read the contribution guide: https://vaadin.com/docs/latest/contributing/overview
• I have added a description following the guideline.
• The issue is created in the corresponding repository and I have referenced it.
• I have added tests to ensure my change is effective and works as intended.
• New and existing tests are passing locally with my change.
• I have performed self-review and corrected misspellings.

Additional for Feature type of change

• Enhancement / new feature was discussed in a corresponding GitHub issue and Acceptance Criteria were created.

[web-padawan]

Thanks for the PR. While it is marked as fix: actually a few files have been added.

@jouni @rolfsmeds Is this something we want to have in 24.0 or 24.1 alpha only?

[Artur-]

There is no need for this in 24.0

[sissbruecker]

Looks good to me. The new modules are kind of a new feature, and could be convenient in apps don't use Flow or Hilla, but still want the Lumo theme apply to the whole page. Not sure if that requires tagging the PR differently though, it seems kind of niche.

[Artur-]

The feature it adds would be that it allows loading all parts of Lumo in the same way, when you want everything applied globally. The ordering is much more relevant to the current issues in Flow though

[jouni]

Minor naming suggestions, and simplified DOM manipulation logic.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication