Proof of Concept: Monitor Component bundle sizes

[jamieomaguire]

Describe your changes (can list changeset entries if preferable)

Allows us to set max limits (in KB) for each of our components, and runs a CI check that fails if any exceed the limits. If they do, all components will be mentioned in a PR comment which contains the failures in a table. It also logs out the gzip and brotli compressed sizes.

I wrote the package to prototype it quickly however there's no reason we can't fork it and move into the monorepo if we wish.

CI Behaviour:

• Lists all failing components
• Adds a comment on failiure
• Updates the existing comment if previous runs added one
• Deletes the existing comment if it previously failed and now passes

Illustrations:

The new CI steps (only run on the Ubuntu Node 20 build)

When all components pass

PR Comment left when components fail

CI logs when a component fails

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9e93da3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[maledr5]

Looking good thanks for putting this together. My only nitpick is I wonder if we could have all the config in 1 file per component and not 2. But other than that looks like a good approach 👍