Setting up local registry functionality

[pacostas]

Summary

This pull request adds to test.sh the option to set up a local registry with crane. Specifically if a file called integration.json exists and it has an attribute called "setup_local_registy": true in it, then, the test.sh script will spawn a local registry on a random available port and export the registry url to an env variable called REGISTRY_URL to make it available for any program that might need to use it. After test.sh has finished, the local registry is being killed.

This is useful for two reasons:

• For the extension, it needs a local registry to push the builder image which later on will be used to build the app.
• For multi-arch, as currently on jammy-tiny-stack repo, in order to generate the receipts, a local registry is needed https://github.com/paketo-buildpacks/jammy-tiny-stack/blob/767e48e7f08cccb843967a2496a19ff5c1622b96/scripts/receipts.sh#L168

The current implementation of creating a local registry has been copied over from the jammy-tiny-stack repo, with the only difference being that the create registry functionality has been moved to a commonplace, the to tools.sh file, as in the near future, it will be used by two scripts, the test.sh (which is currently used by the extension) and the receipts.sh (when the mutli-arch has been implemented for the stacks)

Testing

• Create script has been tested here: https://github.com/pacostas/jammy-base-stack/actions/runs/9662190126/job/26651545500?pr=3
• Update tools actions for stacks, have been tested here: https://github.com/pacostas/github-config/actions/runs/9661661536 (On the test, it does not create a PR as my repo does not have proper configuration, although the create-pr functionality has not been changed therefore, it is not necessary to test it.)

Use Cases

• Extension needing a local registry to push the builder while running acceptance tests.

Checklist

• I have viewed, signed, and submitted the Contributor License Agreement.
• I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
• I have added an integration test, if necessary.
• I have reviewed the styleguide for guidance on my code quality.
• I'm happy with the commit history on this PR (I have rebased/squashed as needed).