Investigate if there is a way to create a build with components on a11y branches

## Summary

Currently if we develop a new component we want the guidance to be released at the same time, but in order for this to happen we need to build the components locally to create the guidance. When we do this and create a PR, there is no build because it can't access the component from npm as it isn't there. But this makes it difficult for everyone to review.

## 💬 Description

There should be some investigation into whether there's anything we can do to get a build up with components that aren't released on npm yet.
Something like the canary release but just for us to use components in the a11y branches?

## 💰 Use value

It'll save more time for people reviewing.

Start by tracing the repository's build and branch workflow, then compare it with the existing canary-release approach. Determine whether an a11y branch can produce a reviewable build using unreleased components; done means the team has a documented, workable approach or a clearly recorded reason it is not feasible.

Written by the indexing model from the issue text.