chore(deps): Bump v6 branch to latest core alpha

[tlabaj]

What: Closes #9411

Additional issues: towards #9811, #9808, and #9809

• Bumped core alphas
• Masthead: Removed backgroundColor prop since light background is now the default with no option to change it.
• NotificationBadge: .pf-v5-c-notification-badge__count no longer has a style associated with it so I updated the code with hardcoded placeholder string.
• PageSidebar: Removed Page sidebar theme prop since it only supports the default theme.
• PageSection: Removed light, dark and `darker variant since the are no longer supported.
• PageHeader (deprecated): removed isSelected prop since it is no longer supported in Page
• Fixed generate tokens to work with new naming

Screenshots of tokens BEFORE:

Screenshots of tokens AFTER:

[patternfly-build]

Preview: https://patternfly-react-pr-9774.surge.sh

A11y report: https://patternfly-react-pr-9774-a11y.surge.sh

[mfrances17]

just some nits, copy/paste error in multiple places :)

[nicolethoen]

it'd be good to double check that any global tokens in the core repo are getting translated appropriately into react-tokens, just like the other css variables.

[srambach]

Notification badges don't look quite right - there's a weird outline and the hover is wrong. But these are also slightly still in flight along with some button work from @mcoker
Page is getting a scrollbar that isn't there in core. That might take a little more investigation.

[nicolethoen]

This is really cool!

couple quick questions:

I see that we are defining the token for blue_100 for example as:

export const _pf_t_color_blue_100 = {
  "name": "--pf-t--color--blue--100",
  "value": "#d9e9ff",
  "var": "var(--pf-t--color--blue--100)"
};
export default _pf_t_color_blue_100;

Will that eventually be renamed and somehow replace the coexisting global variable?:

export const global_palette_blue_100 = {
  "name": "--pf-v5-global--palette--blue-100",
  "value": "#bee1f4",
  "var": "var(--pf-v5-global--palette--blue-100)"
};
export default global_palette_blue_100;

EDIT: this might be exactly what your TODO in the PR description is referring to - so never mind :)

Also, the individual token files look good, but in patternfly_variables.js I see quite a few tokens that have value: undefined such as:

"_pf_t_global_color_nonstatus_orangered_100": {
      "name": "--pf-t--global--color--nonstatus--orangered--100",
      "value": "undefined",
      "values": [
        "--pf-t--color--orangered--200",
        "undefined"
      ]
    },

Is that expected?

[srambach]

I'm still seeing a difference in notification badge. I know there's an upcoming sprint to clean up notification badge but I don't know if there's a problem with what's in this PR or if it will be addressed. The workspace styles to make the dark background can be removed for sure.

Otherwise, it looks ok to me and I'm fine moving forward and circling back.

[tlabaj]

I'm still seeing a difference in notification badge. I know there's an upcoming sprint to clean up notification badge but I don't know if there's a problem with what's in this PR or if it will be addressed. The workspace styles to make the dark background can be removed for sure.

Otherwise, it looks ok to me and I'm fine moving forward and circling back.

@srambach This can be addressed by the issue for notification badge #9811
The goal of the PR was to pull in alphas, make sure it builds and make sure Tokens are generated correctly.

[mfrances17]

LGTM