Add jammy tiny stack support to golang.

[robdimsdale]

Summary

This PR adds the jammy tiny stack to go - which we have validated with a custom-built jammy tiny stack. There is no readily-available jammy tiny stack for CI or external consumption yet.

See also: paketo-buildpacks/go-dist#402

Signed-off-by: Frankie Gallina-Jones frankieg@vmware.com

Use Cases

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).

[sophiewigmore]

Seems reasonable to me if you have tested this locally with success. It's also an easy-enough fix to roll back if we discovered some type of issue with it for some reason.

[loewenstein]

Wondering if go buildpacks could add support for any stack, i.e. *?

[robdimsdale]

@loewenstein I wondered that, but the challenge is there are stacks that the go buildpacks won't work on today (e.g. io.buildpacks.stacks.windows.servercore, from https://github.com/paketo-buildpacks/procfile/blob/bc5a4da26b84cc4c37a2c623bf41c98d5fb0d47f/buildpack.toml#L44)

[loewenstein]

Ok, I see. Seems like this will have to wait for buildpacks/rfcs#219 then.