ci(pie-monorepo): DSW-2400 refactor generate:component-statuses script

[xander-marjoram]

Describe your changes (can list changeset entries if preferable)

• [Added] - Caching for generate:component-statuses build.
• [Added] - New copy:component-statuses script for pie-docs and pie-storybook which copies the status file from the root instead of building it from scratch in three different places.
• [Fixed] - A linting warning in the docs site, and I aligned the exports in a few other files at the same time to avoid the need to disable eslint

copy:component-statuses can be run from the root, or filtered to pie-docs/pie-storybook. It will automatically trigger generate:component-statuses to run.

The generate script uses caching, with the package.json file for all of the components as inputs. So if none of these files have changed, the cache will be hit.

The copy script doesn't use caching because it's just copying a single file, so there isn't really anything to be gained.

Example logs of the build working as expected:

• https://github.com/justeattakeaway/pie/actions/runs/10829301180/job/30046579775?pr=1838#step:4:43
• https://github.com/justeattakeaway/pie/actions/runs/10829301180/job/30046579775?pr=1838#step:4:375

Author Checklist (complete before requesting a review)

• I have performed a self-review of my code
• I have reviewed the PIE Storybook PR preview
• I have reviewed the PIE Docs PR preview

[changeset-bot]

🦋 Changeset detected

Latest commit: 7a80c5e

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

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

[siggerzz]

Minor comments, but happy to merge as is, as I don't think there's any harm in being explicit with which package task needs to run 👍🏼