Add support to define a callback for FIPS test failures instead of aborting the process

[andrewhop]

Description of changes:

This change adds a new build option AWSLC_FIPS_FAILURE_CALLBACK that then requires applications that use AWS-LC to define the AWS_LC_fips_failure_callback(const char* message) function. If that function is not defined AWS-LC fails to load.

When the callback is defined and a FIPS failure (CAST or PWCT) happens AWS-LC calls that function instead. It is up to the calling application to ensure no further cryptographic operations occur. This is not an approved way to use AWS-LC in FIPS mode, for the approved way to build and use AWS-LC see the latest FIPS security policy.

Testing

This change adds a new gtest application that checks the callback function is called with the expected message and is used with break-kat.go and the runtime PCT environment variables to ensure the callback is passed the expected message.

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.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 48.97959% with 25 lines in your changes missing coverage. Please review.

Project coverage is 79.05%. Comparing base (1ada1e3) to head (408f243).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
crypto/fips_callback_test.cc	47.91%	24 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2162      +/-   ##
==========================================
+ Coverage   79.04%   79.05%   +0.01%     
==========================================
  Files         612      613       +1     
  Lines      106238   106376     +138     
  Branches    15010    15025      +15     
==========================================
+ Hits        83974    84096     +122     
- Misses      21613    21628      +15     
- Partials      651      652       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[andrewhop]

I realized I could simplify the testing and put it all in crypto_test. I had to update some of the self_check values to not conflict, e.g. the self_check was using an all zero key and we had another test that had an all zero key so break-kat.go didn't know which one was the real one.