Add out-of-the-box support for the static stack

[robdimsdale]

Describe the Enhancement

The go buildpack works with the static stack/buildpackless builder, but this feature requires some manual configuration (see #769 for details).

It would be better if the relevant component buildpacks in the Go buildpack could automatically set these environment variables when they detect they are running on the static stack.

Possible Solution

This could look similar to how the rust (cargo) buildpack already does this. Essentially look at the stack.id and set env vars as appropriate. I don't think we even need to consider musl for golang - certainly not for the first iteration.

Motivation

This would enable out-of-the-box support on the static stack, which would lower the barrier for users who want this feature. They wouldn't have to read specific documentation or set specific flags.

[robdimsdale]

The @paketo-buildpacks/go-maintainers had quorum and reached a majority consensus on moving this forward.

We agreed to start with the absolute simplest solution - described above - and defer any configuration (e.g. with BP_* environment variables) to a later time.