Enable FIPS compliancy in Makefile

[naemono]

This potential change will enable FIPS compliancy for the operator build by making the changes:

1. Add an ENABLE_FIPS environment variable which will add a build flag goexperiment.boringcrypto to the existing GO_TAGS variable which we use during go build and docker build operations.
2. Append -fips to all container build names that we push to existing registries.
3. Adjusts the release pipeline in Jenkins to run another docker build operation with ENABLE_FIPS=true environment variable set.

This change does not

1. Add any Jenkins/Buildkite changes that would allow FIPS these changes to be triggered in our current/future CI system.

[naemono]

Would it make sense to do a whole other step here, with a different target in setenvconfig? It seems overkill when looking at this, but setenvconfig is used to set all env variables in all other steps, but since the build case block is split between nightly and release already, it seemed adding a 3rd would be ugly.

[thbkrkr]

I'm good with this approach to call again the build in FIPS mode using an environment variable. I don't think we should rely on setenvconfig for this. Also I wonder if we should not make this builds in parallel with the old one.

stage('build') {
    failFast true
    parallel {
        stage("build operator image") {
            steps {
                sh '.ci/setenvconfig build'
                sh 'make -C .ci license.key TARGET=ci-release ci'
            }
        }
        stage("build operator image in FIPS mode") {
            steps {
                sh '.ci/setenvconfig build'
                sh 'make -C .ci license.key TARGET=ci-release ci ENABLE_FIPS=true'
            }
        }
    }
}

[naemono]

I think the parallel build makes perfect sense. I've updated this PR with this new parallel build phase.

[thbkrkr]

LGTM