[CU] Update yarn and tweak Storybook

[TimRoe]

Associated with Ticket 7194 but did not address the goal, just committing useful changes made alongside attempting that.

Description of Change

Changes by proxy to attempting to "Explore Improved Components Package Publish Config" which didn't pan out.

Changes made:

• Updated yarn from 3.6.1 to 4.0.2
• Added logic to suppress showing the change background color button that was bugged
  • Added note to ticket 7368 reflecting this change as it'll need to be reverted if/when that is resolved

Testing Packages

• 0.3.6-alpha.7
• 0.3.6-alpha.8
• 0.3.6-alpha.9

Testing

• Tested on iOS
• Tested on Android
• Tested on Web

PR Checklist

Code reviewer validation:

• General
  • PR is linked to ticket(s)
  • PR has changelog label applied if it's to be included in the changelog
  • Acceptance criteria:
    • All satisfied or
    • Documented reason for not being performed or
    • Split to separate ticket and ticket is linked by relevant AC(s)
  • Above PR sections adequately filled out
  • If any breaking changes, in accordance with the pre-1.0.0 versioning guidelines: a CU ticket has been created for the VA Mobile App detailing necessary adjustments with the package version that will be published by this ticket
• Code
  • Tests are included if appropriate (or split to separate ticket)
  • New functions have proper TSDoc annotations

Publish

Does not warrant a new version per the versioning guidelines as it is just repo-level and storybook configuration changes; does not alter anything shippable except the packageManager line of the package.json which shouldn't matter.

[narin]

Looks good. Just some clarifying questions.

[narin]

What's the benefit of disabling this?

[TimRoe]

No idea, the changes it made to this file happened automatically when I ran yarn set version 4.0.2.

[narin]

Any reason we're not using 0 (the default)? Seems to be the fastest according to the docs.

[TimRoe]

Same logic as above--it set it automatically running the update command. Testing shifting to 0 was fairly slow on a first run (updating every checksum in yarn.lock), but faster on subsequent run.

[TimRoe]

some clarifying questions

Updated both locally (read: deleted to use the default), will do a quick draft test tomorrow to make sure nothing seems broken and commit if it seems good.