[Theme][EuiVisColorStore] Fix wrong initial hasVisColorAdjustment value

[mgadewoll]

Summary

This PR fixes the initial value for the static initialized EUI_VIS_COLOR_STORE. When we updated the default theme from Amsterdam to Borealis, we missed updating this flag value.

This resulted in wrong initial values for color palette calculations which surfaced specifically in tests that use staticeuiPalette... functions and would not be updated with a React component render.

This PR also updates the palette function tests to assert a calculated color which would catch regression issues based on those theme flags.

Why are we making this change?

Fixing unexpected initial color palette values.

Screenshots

ℹ️ The screenshots show:

• euiPaletteForTemperature(6)
• useEuiPaletteForTemperature(6)

before	after

Impact to users

⚠️ This is not a breaking change but it likely results in test/snapshot failures on Kibana side when tests assert based on static color palettes. This is expected and would have happened earlier if we wouldn't have missed this flag update.

UI output would only be affected in non-react-component usages as usages within any React component would update correctly on render of the component based on the euiTheme context update.

QA

• CI passes
• checkout this PR and run Storybook
  • log the values of e.g. euiPaletteForTemperature(6) and useEuiPaletteForTemperature(6) and verify both have the same values (previously the static palette function would differ)

General checklist

• Browser QA
  • Checked in both light and dark modes
  • Checked in both MacOS and Windows high contrast modes
    • (emulate forced colors if you do not have access to a Windows machine.)
  • Checked in mobile
  • Checked in Chrome, Safari, Edge, and Firefox
  • Checked for accessibility including keyboard-only and screenreader modes
• Docs site QA
  • Added documentation
  • Props have proper autodocs (using @default if default values are missing) and playground toggles
  • Checked Code Sandbox works for any docs examples
• Code quality checklist
  • Added or updated jest and cypress tests
  • Updated visual regression tests
• Release checklist
  • A changelog entry exists and is marked appropriately.
  • If applicable, added the breaking change issue label (and filled out the breaking change checklist)
• Designer checklist
  • If applicable, file an issue to update EUI's Figma library with any corresponding UI changes. (This is an internal repo, if you are external to Elastic, ask a maintainer to submit this request)

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: e032228
• Documentation website

cc @mgadewoll

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: e032228

cc @mgadewoll

[weronikaolejniczak]

The code looks alright. Awesome catch, Lene! 🟢 Thank you for adding the unit tests to safe-guard against this in the future.

	Before	After
euiPaletteForTemperature(6)	["#61a2ff", "#90bdff", "#bdd7ff", "#ffc2bb", "#fc9b92", "#f6726a"]	["#61a2ff", "#a8caff", "#e8f1ff", "#ffe8e5", "#ffafa6", "#f6726a"]
useEuiPaletteForTemperature(6)	["#61a2ff", "#a8caff", "#e8f1ff", "#ffe8e5", "#ffafa6", "#f6726a"]	["#61a2ff", "#a8caff", "#e8f1ff", "#ffe8e5", "#ffafa6", "#f6726a"]

I'm wondering about the hasVisColorAdjustment flag, what do we need it for?

[mgadewoll]

I'm wondering about the hasVisColorAdjustment flag, what do we need it for?

@weronikaolejniczak We introduced it to handle differences between Amsterdam and Borealis as we needed to align tokens and color palette generations between those but they had differences (meaning Amsterdam had some random color choices that otherwise couldn't be kept in parity 😅)