feat: Add multi-arch support, update run-image, and streamline build process

[SalimKayal]

This pull request introduces several enhancements to the buildpacks, builder, and run image:

• ARM64 Architecture Support: Enabled linux/arm64 targets for the buildpacks, allowing them to be built and run on ARM64 architectures. The publishing scripts (publish_builder.sh, publish_buildpack.sh) have also been updated to remove the explicit --target "linux/amd64" flag, which should allow pack to build for all supported targets by default.
• Run Image Update: The base run image in run-image/Dockerfile has been updated from paketobuildpacks/run-jammy-full:latest to paketobuildpacks/run-jammy-full:0.1.99.
• Dockerfile Improvements:
  • wget and tini have been added to the apt-get install commands in the run-image/Dockerfile for broader utility.
  • A userdel command ((userdel $(getent passwd ${user_id}|cut -d: -f1) || true)) was added before groupadd and useradd to ensure cleaner user management during image creation.
• Tini Dependency Adjustment: The tini dependency has been removed from the [[requires]] section in buildpacks/ttyd/bin/detect, as tini is now universally installed in the run-image/Dockerfile.

These changes aim to improve platform compatibility, update core components, and streamline the overall build and packaging process.

[olevski]

Thanks Salim this looks really nice. I have 2 questions just so I understand why we are making some of the changes.

Also we should probably also be running the tests on arm runners just to be safe. But this is for a followup in a spearate PR at some other time.

[olevski]

question: why remove this? If it is already there I think then it won't be installed. I think with the changes you have made with this and by adding tini to the run image then you make the buildpacks only work with our run image. I was hoping we can keep things as general as possible.

[SalimKayal]

tini is not multi-arch in paketo's buildpack. I could make my own tini buildpack instead if it's any useful

[SalimKayal]

quick note : the tests can't pass because the run image has changed and that the change is not yet reflected in the registry. See #105