Buildx bake with goss test runner orchestration

[ianpittwood]

Closes #714
Closes #717

Apologies in advance for the sheer size of this PR. Unfortunately, I didn't see a great way to break up the build changes without putting the repo in an awkward state.

Adds

• Implements docker buildx bake for build orchestration. bake files are broken up into docker-bake.hcl (Release image builds), docker-bake.preview.hcl (Preview image builds), and content/docker-bake.hcl (Content image builds). All existing image builds have been recreated in bake. By implementing bake, we should resolve sanity issues around image layering in CI since base image artifacts are explicitly passed to downstream image builds and will not pull from a registry.
• Implements a Python script (./tools/test_bake_artifacts.py) for running tests based off a generated build plan from bake.
• Adds new just targets for building and testing bake builds.

Changes

• Modifications to run_tests.sh scripts for compatibility with new build/test flow.
• MOdifications to goss.yaml files across several projects, mostly increasing timeouts on slow elements like jupyter tests.

Removes

• Existing build workflows including build-content.yaml, build-prerelease.yaml, build-release.yaml, build-workbench-aml.yaml, and build-workbench-gcw.yaml.
• Individual Justfiles in product directories.
• docker-compose.test.yml files in product directories. These have been replaced with the ./tools/test_bake_artifacts.py script.

[costrouc]

I enjoy they way this is structured. I was able to run build locally.

I can see how you thought about how the actions are structured using composite actions and it is much easier for me to follow. So nice to see how fast certain actions finish.

This is a significant step towards simplifying development! Long term I hope that preview and regular builds can be the same bake. I get how for now this is not possible.