Add support to delocate.go to parse output from GCC 11 and test with AL2022

[andrewhop]

Issues:

Resolves CryptoAlg-1482

Description of changes:

1. Add support for the GCC 11 FIPS static build by handling pinsrq instructions
2. Update error message to make it a bit easier to figure out if similar new instructions get misclassified in the future
3. Add AL2022 base image
4. Add AL2022 images with gcc and clang
5. Update CDK to run the regular build and fips build with each compiler (4 new builds)

Call-outs:

None

Testing:

Built images locally and ran tests. Working on deploying the CI to my account next.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and
the ISC license.

[ottok]

I have not reviewed the code nor tested it but I +1 that the bug is relevant and it is important for AWS-LC to test every commit on Amazon Linux 2022 and so that downstream projects/users of AWS-LC on any version of Amazon Linux can "just use it" without extra work.

[sdkellyAWS]

Why does this require llvm? Also why version 15 when the al2022 version of clang is 14?

[andrewhop]

To run the memory sanitizer without false positives from inside the C standard functions we need to compile libc as a part of our build. I didn't think about the clang 14 vs llvm 15. This only needs the libcxx and libcxxabi parts, but it makes more sense to use the matching set.

[andrewhop]

Turns out nothing was using this and trying to add the sanitizer results in C++11 vs 17 version issues. I'll tackle this all later.