NR-291019 add fips compliant package builds

[rajrohanyadav]

What?

Adds compilation and packaging of FIPS compliant packages using boringcrypto

Why?

Many customers can only use FIPS compliant packages in their environments

How?

• use a new Dockerfile to build FIPS and non-FIPS packages
• update goreleaser config to build and package FIPS compliant packages in addition to the normal packages
• Update release workflow to use the same format as infra-agent for coverage.

[gsanchezgavier]

thanks just left a couple of comments, i see that there is no workflow to run this neither push the artifacts. i guess that it would be following prs ?

[rajrohanyadav]

thanks just left a couple of comments, i see that there is no workflow to run this neither push the artifacts. i guess that it would be following prs ?

Thanks for the comments. I believe goreleaser takes care of pushing the artifacts to the release from the runner (as happening until now for this repo). I don't know if we need to publish these to S3. So, there would be no changes to the way packages are published, just two additional packages with be created for each release.

[alvarocabanas]

I left some comments

[alvarocabanas]

LGTM, GOOD JOB!