Weigh pros and cons of default density included in alpha

[taysea]

In future, we'd like to support "densities" as a mode, but we're not ready to support various densities yet.

Bias is towards only including something now if it's necessary. Ideally we could just add it later.

Deliverables:

• [x] Document pros/cons of including "density" as a collection now with a "default" mode vs leaving it out when it comes to Figma publishing/designer workflow: https://github.com/grommet/hpe-design-system/issues/4148#issuecomment-2344526062
• [x] Propose if we should include "density" now or add it later: https://github.com/grommet/hpe-design-system/issues/4148#issuecomment-2344526062

[taysea]

For “beta” release if we publish “spacing” values from the “dimension” collection (aka no density tokens yet):
 Scenario: A product designer applies a spacing token such as “spacing.medium” to their auto layout

--> In future if we add “density” collection, and “hide” dimension tokens from publishing:

Outcome: Anywhere the product designer has applied the old “spacing.medium”

• That token will stay applied/”locked” and any changes to the dimension “spacing.medium” will still feed through.
• Once they change that variable to use the new “density” spacing tokens, then the old “dimension” variables will not be able to be accessed.
• The main takeaway is it won’t “break” their design but they just won’t be able to leverage “density” until they re-apply with the new density tokens.

Proposal is we don't need to add density pre-alpha release and we can discuss as a broader group when we want to introduce them.