Dynamically resolve Amazon Lambda arch

[Art051]

I encountered some issues running Quarkus lambda tutorials on Macbook with M2 Pro chip, and saw a similar issue reported here: #38715

This PR fixes these issues:

• Extract the major version number for the build, appending to the Java runtime variable (quarkus supports 17 and 21, but 11 was hard coded previously) this will retrieve the version from the developer's device and append it to the necessary variable.
• Set the native runtime to a variable for easier identification, with comment indicating where to find the current options
• Added detection and setting of architecture based on machine being used to build the lambda

[Art051]

I fixed the merge conflict and marked as resolved and committed the change. But now there's a bot check error regarding the merge commit existing. But I've no idea how to resolve it, any pointers?

[Art051]

@patriot1burke Any chance for a re-review?

[Art051]

@patriot1burke Apologies - it's requiring manual workflow approval by a maintainer too: CI Sanity Check Expected — Waiting for status to be reported

[gsmet]

Sorry it took so long. I approved the workflow, let's wait for CI to get green and merge.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit cf5774c.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[Art051]

Sorry it took so long. I approved the workflow, let's wait for CI to get green and merge.

No problem at all, cheers for sorting it out!