UI: Fix about page layout

[cdedreuille]

What I did

This PR fixes some layout regression on the about page and on the closing button on pages (top right):

• Fix alignments in the about page on desktop
• Replace buttons with the correct ones in multiple places
• Fix the "What's new" footer buttons
• Fix close button alignment by removing Flexbar. We will deprecate this component very soon.
• Replaced Storybook icon + text with Storybook logo
• Fix SidebarIconButton styles
• Remove ToolbarMenu - Not used anymore anywhere.

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

1. Open Storybook UI
2. Check that all alignments and spacings are correct both on desktop and mobile

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

[shilman]

@cdedreuille why are you using the ci: daily label? I think ci: normal would be sufficient and it consumes a LOT fewer resources!

[cdedreuille]

@shilman Mostly because @JReinhold told me so 😅. I can use ci:normal going forward.