feature: create FIPS complaint linux image

[Arlington1985]

Issue #, if available:
NA
Description of changes:
New FiPS complaint docker image based on Linux AMI 2 and tagged as fips-latest

Tested
Temporarily GO installed inside fips relesed image to test FIPS complaincy of FluentBit binaries:

(venv) ➜  aws-for-fluent-bit git:(fips-image) ✗ docker run -it --rm amazon/aws-for-fluent-bit:fips-latest  /bin/bash
bash-4.2# go tool nm /fluent-bit/firehose.so | grep FIPS
  5f6948 t BORINGSSL_FIPS_abort
  5f32b4 t FIPS_mode_set
  5f32c0 t FIPS_read_counter
  5b61cc T _cgo_14d622f8b473_Cfunc__goboringcrypto_FIPS_mode
  5f32ac t _goboringcrypto_FIPS_mode
  2433c0 t crypto/internal/boring._Cfunc__goboringcrypto_FIPS_mode.abi0
  ca0ea8 d crypto/internal/boring._cgo_14d622f8b473_Cfunc__goboringcrypto_FIPS_mode
  ca5c80 d crypto/tls.defaultCipherSuitesFIPS
  ca5c40 d crypto/tls.defaultCurvePreferencesFIPS
  ca5c60 d crypto/tls.defaultSupportedSignatureAlgorithmsFIPS
  ca5c20 d crypto/tls.defaultSupportedVersionsFIPS
  ca38c0 d github.com/aws/aws-sdk-go/aws/session.awsUseFIPSEndpoint
  4df180 t github.com/aws/aws-sdk-go/aws/session.setUseFIPSEndpointFromEnvVal

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[swapneils]

Can you specify which are the substantive changes that make this image FIPS compliant, either here in the conversation or as comments in the code?

[Arlington1985]

Can you specify which are the substantive changes that make this image FIPS compliant, either here in the conversation or as comments in the code?

The GOEXPERIMENT=boringcrypto environment variable in Go selects the upstream BoringCrypto backend as a cryptographic library for a program