Test .NET 6 + Jammy Jellyfish

[fg-j]

Summary

The Paketo Jammy Stacks RFC has been accepted, and specifies that the Jammy Full and Base stacks will have the stack ID io.buildpacks.stacks.jammy. .NET 3.1 does not work on Jammy Jellyfish because it requires an outdated version of OpenSSL. So, this PR adds an integration test that ensure we can compile and run a .NET 6 source code app on Jammy Jellyfish.

Use Cases

This marks official Jammy support for the .NET Core buildpack.

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

[fg-j]

Blocked by

• Add Jammy stack to .NET 6 dependencies dotnet-core-runtime#349
• Add Jammy stack to .NET 6 dependencies dotnet-core-aspnet#346
• Add Jammy stack to .NET 6 dependencies dotnet-core-sdk#365
• Add Jammy stack to dependencies icu#275
• Support wildcard stack dotnet-publish#331
• Support wildcard stack dotnet-execute#324
• Support for Jammy Jellyfish node-engine#487

[sophiewigmore]

@paketo-buildpacks/dotnet-core-maintainers unblocked by the latest Node Engine buildpack release