Use new build tag to differentiate dynamic build

When we linked to libvirt directly, having the libvirt platform in the
build was synonymous with a dynamically linked build. Now that we use a
pure-Go libvirt library, the build type can be independent of whether
libvirt is included.

Once the baremetal installer build no longer includes the libvirt
platform, we still want it to be dynamically linked.

Author: zaneb

hack/build.sh

@@ -113,7 +113,7 @@ then
 	GOOS='' GOARCH='' go generate ./data
 fi
 
-if (echo "${TAGS}" | grep -q 'libvirt')
+if (echo "${TAGS}" | grep -q '\bfipscapable\b')
 then
 	export CGO_ENABLED=1
 fi

images/baremetal/Dockerfile.ci

@@ -2,7 +2,7 @@
 # It builds an image containing openshift-install.
 
 FROM registry.ci.openshift.org/ocp/builder:rhel-8-golang-1.21-openshift-4.16 AS builder
-ARG TAGS="libvirt baremetal"
+ARG TAGS="libvirt baremetal fipscapable"
 WORKDIR /go/src/github.com/openshift/installer
 COPY . .
 RUN DEFAULT_ARCH="$(go env GOHOSTARCH)" hack/build.sh

images/libvirt/Dockerfile.ci

@@ -3,7 +3,7 @@
 # oc for getting assets from an existing cluster to spin up multi-architecture compute clusters on libvirt.
 
 FROM registry.ci.openshift.org/ocp/builder:rhel-8-golang-1.21-openshift-4.16 AS builder
-ARG TAGS="libvirt"
+ARG TAGS="libvirt fipscapable"
 WORKDIR /go/src/github.com/openshift/installer
 COPY . .
 RUN DEFAULT_ARCH="$(go env GOHOSTARCH)" hack/build.sh

pkg/hostcrypt/dynamic.go

@@ -1,5 +1,5 @@
-//go:build libvirt
-// +build libvirt
+//go:build fipscapable
+// +build fipscapable
 
 package hostcrypt
 

pkg/hostcrypt/static.go

@@ -1,5 +1,5 @@
-//go:build !libvirt
-// +build !libvirt
+//go:build !fipscapable
+// +build !fipscapable
 
 package hostcrypt