Pull in updated spacing and container tokens

[taysea]

Deploy Preview

What does this PR do?

• Pulls in updated spacing and container tokens based on Spacing — Define rationale for which values from generated scale are part of semantic set #4487
• For grommet-app/theme, maintains backwards compatibility with existing t-shirt sizes

Where should the reviewer start?

What testing has been done on this PR?

In addition to the feature you are implementing, have you checked the following:

General UX Checks

• Small, medium, and large screen sizes
• Cross-browsers (FireFox, Chrome, and Safari)
• Light & dark modes
• All hyperlinks route properly

Accessibility Checks

• Keyboard interactions
• Screen reader experience
• Run WAVE accessibility plugin (Chrome)

Code Quality Checks

• Console is free of warnings and errors
• Passes E2E commit checks
• Visual snapshots are reasonable

How should this be manually tested?

Any background context you want to provide?

What are the relevant issues?

Closes #4543

Screenshots (if appropriate)

Should this PR be mentioned in Design System updates?

Is this change backwards compatible or is it a breaking change?

[changeset-bot]

🦋 Changeset detected

Latest commit: 5e46c19

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
hpe-design-tokens	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[netlify]

✅ Deploy Preview for unrivaled-bublanina-3a9bae ready!

Name	Link
🔨 Latest commit	5e46c19
🔍 Latest deploy log	https://app.netlify.com/sites/unrivaled-bublanina-3a9bae/deploys/678fe235758ef70008d22590
😎 Deploy Preview	https://deploy-preview-4702--unrivaled-bublanina-3a9bae.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[halocline]

A couple questions, rest looks good.

[halocline]

The primitive token to value pattern seems to break here. If I understand how these primitive tokens are being built up, there is a ratio of 25 between the token and value (e.g. 600 / 25 = 24, 25600 / 25 = 1024).

However, 38400 & 76800 seem to break this pattern. 38400 / 25 = 1536, not 1152 as currently defined; 76800 / 25 = 3072, not 1536.

Do we need to:

• add 28800 --> 1152
• modify 38400 --> 1536
• add 51200 --> 2048
• modify 78600 --> 3072

[taysea]

Good catch. Yes 38400 --> 1536. I don't believe we have use for 1152, 2048, or 3072.

I've adjusted 38400, but not added the others.

[halocline]

I'm good with omitting those for now.

We don't need the 1152 because we are just hardcoding that in the HPE theme, correct?

[taysea]

Exactly. 👍