Investigate multi-arch image support in our workflows

[sophiewigmore]

In #108 @dmikusa added ARM64 support for the Jammy Tiny stack. Even though we can successfully build a multi-arch stack using the jam functionality, other parts of the create-release workflow fail (example) due to issues with Syft and multi-arch image support.

Before we can officially ship multi-arch stack images, we need to understand how this will play with our full stack creation workflow, as other issues could crop up besides just the issue with Syft during package receipt collection.

This issue is to test out the different parts of the stack creation workflow with a multi-arch image and to either:
A) file issues to enable the workflow as-is to work with multi arch, or
B) come up with a plan of how we'd need to re-architect our stack release process to enable multi-arch releases (and file issues for this work)

[sophiewigmore]

@jericop has been working on this with his various PRs:
#131
#136
#137
#138
#140
#142

[sophiewigmore]

To do:

• deal with multi arch receipts (Fix package receipts generated in create-release workflow #136 (comment)_
• update .syncignore + enable all workflows

[sophiewigmore]

status update - this is 95% done, I have a couple small bug to work out and then this will be done
https://github.com/paketo-buildpacks/jammy-tiny-stack/actions/runs/8944156775/job/24570715602

[sophiewigmore]

this is complete for the Jammy Tiny stack