Build kanister-tools Go binaries in fipsonly mode

[sukhil-suresh]

Change Overview

The kanister-tools image is shipped with 3 binaries - restic, kopia and kando. They are already built to use the
goboring library. This PR makes changes to restrict all TLS configurations to FIPS-approved settings for these binaries.

• Modified docker/tools/Dockerfile for building restic and kopia in fipsonly mode
• Added cmd/kando/fipsonly.go and updated .goreleaser.yaml for building kando in fipsonly mode

Pull request type

• 🌈 Refactoring (no functional changes, no api changes)
• 🐹 Trivial/Minor

Test Plan

• 💪 Manual

Manually verified that the kanister-tools binaries were built in fipsonly mode using the goversion tool.

• Built kando in a Linux container:

  $ goreleaser build --id kando --rm-dist --debug --snapshot
  

• Copied newly built kando and LICENSE (from root folder) to docker/tools folder
• Built fipsonly kanister-tools image:

  $ docker build -t kanister-tools docker/tools
  

• Copied binaries over from kanister-tools container:

  $ docker create --name debug kanister-tools
  
  $ docker cp debug:/usr/local/bin/restic .
  $ docker cp debug:/usr/local/bin/kopia .
  $ docker cp debug:/usr/local/bin/kando .
  

• Verified binaries were in fipsonly mode:

  $ goversion --crypto restic | grep fips     
  restic go1.21.4 X:boringcrypto (standard crypto) +crypto/tls/fipsonly
  
  $ goversion --crypto kando | grep fips
  kando go1.21.3 X:boringcrypto (boring crypto) +crypto/tls/fipsonly
  
  $ goversion --crypto kopia | grep fips
  kopia go1.21.4 X:boringcrypto (boring crypto) +crypto/tls/fipsonly
  

  The goversion tool was installed from the master branch of https://github.com/rsc/goversion.

[sukhil-suresh]

@pavannd1 this PR never got merged.

[pavannd1]

@Mergifyio update

[mergify]

update

❌ Pull request can't be updated with latest base branch changes

Mergify needs the author permission to update the base branch of the pull request.
@sukhil-suresh needs to authorize modification on its head branch.

[sukhil-suresh]

@pavannd1 I enabled the Allow edits by maintainers. Can you try again, please?