Align Initializr theme styling with design language tokens

[liannacasper]

Motivation

• Ensure the Initializr UI follows the project design language so light and dark modes use the same semantic token palette and visual rules.
• Make selection/interaction states consistently use the documented blue accent and reserve lime for the primary confirmation action.
• Avoid changing UIID names so existing runtime logic and tests that map UIIDs continue to work.

Description

• Updated scripts/initializr/common/src/main/css/theme.css to replace literal color values with the design guide palette for light and dark modes (backgrounds, panels, inputs, preview surfaces, borders, and text colors).
• Converted interaction/selection/pressed states to use blue accents (e.g. #2F6BFF, #4D86FF) and adjusted dark-mode borders/strong borders to #4C6EA8/#7390C0 respectively.
• Switched the primary action button styling to the design guide’s lime confirmation color (#B8D532) and updated its pressed state, and adjusted subtle surfaces/secondary buttons to the documented light/dark tokens.
• Preserved existing UIID names and class selectors so Java mapping and tests remain valid while visual tokens were aligned to the docs.

Testing

• Ran mvn -pl common -Dtest=InitializrThemeInteractionTest,TemplatePreviewPanelThemeTest test -DfailIfNoTests=false which failed because the reactor-built dependency initializr-ZipSupport could not be resolved.
• Ran mvn -pl common -am -Dtest=InitializrThemeInteractionTest,TemplatePreviewPanelThemeTest test -DfailIfNoTests=false which failed during the build because the Ant task attempted to download UpdateCodenameOne.jar and the environment returned java.net.SocketException: Network is unreachable.
• No automated unit tests in this environment passed due to the dependency and network limitations described above.

---

Codex Task

[github-actions]

Cloudflare Preview

• URL: https://pr-4756-website-preview.codenameone.pages.dev
• Branch: pr-4756-website-preview