BigSky logo: adhere to the common logo specs

[ciampo]

Follow-up to #103546 (comment)
Related to DS-216

Proposed Changes

Tweak the BigSkyLogo.Mark logo props in order to follow the latest specs (defined in DS-216):

• centralized common logo prop types;
• removed normalized variant;
• added aria-labelledby to the SVG element pointing to the title;
• optimized the path by running the SVG through SVGOMG
• make the white part of the logo an actual mask when non-monochrome;
• removed "logo" from the default title;
• tweaked the way the export is built, and added a named export to allow Storybook to better extract prop types for controls;
• forwarded ref
• removed unnecessary Storybook examples;
• CHANGELOG

Why are these changes being made?

To stick to the logo API specs (see DS-216)

Testing Instructions

Load Storybook, make sure:

• the component looks and works as on trunk (apart from the lack of normalized);
• controls are shown;
• the component has a aria-labelledby prop when the title is defined;
• the component's central "white" shape becomes a pass-through mask when monochrome="true"

In Calypso:

• Follow instructions from New site: Add BigSky CTA #103546, make sure the logo still looks good in this PR

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-145389

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-145389&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-145389&env=a8c-for-agencies

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• blaze-dashboard
• happy-blocks
• help-center
• odyssey-stats
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug fix/blue-sky-logo on your sandbox.

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Async-loaded Components (~137 bytes removed 📉 [gzipped])

name                                                      parsed_size           gzip_size
async-load-calypso-components-sites-add-new-site-content       -443 B  (-5.5%)     -137 B  (-4.8%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[aduth]

LGTM

[aduth]

Why do we trim() ? I feel like we should expect consumers to pass a well-formed string. And if this is part of the truthiness checks, I'd rather we handle this as a properly-empty nullish value rather than an empty string.

Also, is the idea with a falsey title that it'd be used as a decorative image? And if so, would we also need to hide it from assistive technology (e.g. aria-hidden, role=presentation) ? Or should we just not support the falsey title altogether?

[ciampo]

Good points.

• I removed the trim() call, but kept title as a pure string
• I added more explicit documentation about using aria-hidden as the recommended way to remove from assistive technology

This approach follows the specs that from DS-216 (which originated from this conversation), although I'm happy to revisit the specs if we think they could be improved