Bump sops version to 3.12.1

[jenkins-infra-updatecli]

Bump sops version

Update the `sops` version in the tools-versions.yml file

change detected: * key "$.sops_version" updated from "3.11.0" to "3.12.1", in file "provisioning/tools-versions.yml"

v3.12.1

## Installation

To install `sops`, download one of the pre-built binaries provided for your platform from the artifacts attached to this release.

For instance, if you are using Linux on an AMD64 architecture:

```shell
# Download the binary
curl -LO https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.linux.amd64

# Move the binary in to your PATH
mv sops-v3.12.1.linux.amd64 /usr/local/bin/sops

# Make the binary executable
chmod +x /usr/local/bin/sops
```

### Verify checksums file signature

The checksums file provided within the artifacts attached to this release is signed using [Cosign](https://docs.sigstore.dev/cosign/overview/) with GitHub OIDC. To validate the signature of this file, run the following commands:

```shell
# Download the checksums file, certificate and signature
curl -LO https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.12.1.checksums.txt \
  --certificate sops-v3.12.1.checksums.pem \
  --signature sops-v3.12.1.checksums.sig \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com
```

### Verify binary integrity

To verify the integrity of the downloaded binary, you can utilize the checksums file after having validated its signature:

```shell
# Verify the binary using the checksums file
sha256sum -c sops-v3.12.1.checksums.txt --ignore-missing
```

### Verify artifact provenance

The [SLSA provenance](https://slsa.dev/provenance/v0.2) of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through an [in-toto](https://in-toto.io/) link metadata file named `sops-v3.12.1.intoto.jsonl`. To verify the provenance of an artifact, you can utilize the [`slsa-verifier`](https://github.com/slsa-framework/slsa-verifier#artifacts) tool:

```shell
# Download the metadata file
curl -LO  https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.12.1.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.12.1
```

## Container Images

The `sops` binaries are also available as container images, based on Debian (slim) and Alpine Linux. The Debian-based container images include any dependencies which may be required to make use of certain key services, such as GnuPG, AWS KMS, Azure Key Vault, and Google Cloud KMS. The Alpine-based container images are smaller in size, but do not include these dependencies.

These container images are available for the following architectures: `linux/amd64` and `linux/arm64`.

### GitHub Container Registry

- `ghcr.io/getsops/sops:v3.12.1`
- `ghcr.io/getsops/sops:v3.12.1-alpine`

### Quay.io

- `quay.io/getsops/sops:v3.12.1`
- `quay.io/getsops/sops:v3.12.1-alpine`

### Verify container image signature

The container images are signed using [Cosign](https://docs.sigstore.dev/cosign/overview/) with GitHub OIDC. To validate the signature of an image, run the following command:

```shell
cosign verify ghcr.io/getsops/sops:v3.12.1 \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  -o text
```

### Verify container image provenance

The container images include [SLSA provenance](https://slsa.dev/provenance/v0.2) attestations. For more information around the verification of this, please refer to the [`slsa-verifier` documentation](https://github.com/slsa-framework/slsa-verifier#containers).

## Software Bill of Materials

The Software Bill of Materials (SBOM) for each binary is accessible within the artifacts enclosed with this release. It is presented as an [SPDX](https://spdx.dev/) JSON file, formatted as `<binary>.spdx.sbom.json`.

## What's Changed
* Release 3.12.1 by @felixfontein in https://github.com/getsops/sops/pull/2080
* Many more changes, see [CHANGELOG.md for 3.12.0](https://github.com/getsops/sops/blob/main/CHANGELOG.md#3120).

**Full Changelog**: https://github.com/getsops/sops/compare/v3.11.0...v3.12.1

Update the `sops` version in the goss test

change detected: * key "$.command.sops.stdout[0]" updated from "3.11.0" to "3.12.1", in file "tests/goss-linux.yaml"

v3.12.1

## Installation

To install `sops`, download one of the pre-built binaries provided for your platform from the artifacts attached to this release.

For instance, if you are using Linux on an AMD64 architecture:

```shell
# Download the binary
curl -LO https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.linux.amd64

# Move the binary in to your PATH
mv sops-v3.12.1.linux.amd64 /usr/local/bin/sops

# Make the binary executable
chmod +x /usr/local/bin/sops
```

### Verify checksums file signature

The checksums file provided within the artifacts attached to this release is signed using [Cosign](https://docs.sigstore.dev/cosign/overview/) with GitHub OIDC. To validate the signature of this file, run the following commands:

```shell
# Download the checksums file, certificate and signature
curl -LO https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.12.1.checksums.txt \
  --certificate sops-v3.12.1.checksums.pem \
  --signature sops-v3.12.1.checksums.sig \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com
```

### Verify binary integrity

To verify the integrity of the downloaded binary, you can utilize the checksums file after having validated its signature:

```shell
# Verify the binary using the checksums file
sha256sum -c sops-v3.12.1.checksums.txt --ignore-missing
```

### Verify artifact provenance

The [SLSA provenance](https://slsa.dev/provenance/v0.2) of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through an [in-toto](https://in-toto.io/) link metadata file named `sops-v3.12.1.intoto.jsonl`. To verify the provenance of an artifact, you can utilize the [`slsa-verifier`](https://github.com/slsa-framework/slsa-verifier#artifacts) tool:

```shell
# Download the metadata file
curl -LO  https://github.com/getsops/sops/releases/download/v3.12.1/sops-v3.12.1.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.12.1.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.12.1
```

## Container Images

The `sops` binaries are also available as container images, based on Debian (slim) and Alpine Linux. The Debian-based container images include any dependencies which may be required to make use of certain key services, such as GnuPG, AWS KMS, Azure Key Vault, and Google Cloud KMS. The Alpine-based container images are smaller in size, but do not include these dependencies.

These container images are available for the following architectures: `linux/amd64` and `linux/arm64`.

### GitHub Container Registry

- `ghcr.io/getsops/sops:v3.12.1`
- `ghcr.io/getsops/sops:v3.12.1-alpine`

### Quay.io

- `quay.io/getsops/sops:v3.12.1`
- `quay.io/getsops/sops:v3.12.1-alpine`

### Verify container image signature

The container images are signed using [Cosign](https://docs.sigstore.dev/cosign/overview/) with GitHub OIDC. To validate the signature of an image, run the following command:

```shell
cosign verify ghcr.io/getsops/sops:v3.12.1 \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  -o text
```

### Verify container image provenance

The container images include [SLSA provenance](https://slsa.dev/provenance/v0.2) attestations. For more information around the verification of this, please refer to the [`slsa-verifier` documentation](https://github.com/slsa-framework/slsa-verifier#containers).

## Software Bill of Materials

The Software Bill of Materials (SBOM) for each binary is accessible within the artifacts enclosed with this release. It is presented as an [SPDX](https://spdx.dev/) JSON file, formatted as `<binary>.spdx.sbom.json`.

## What's Changed
* Release 3.12.1 by @felixfontein in https://github.com/getsops/sops/pull/2080
* Many more changes, see [CHANGELOG.md for 3.12.0](https://github.com/getsops/sops/blob/main/CHANGELOG.md#3120).

**Full Changelog**: https://github.com/getsops/sops/compare/v3.11.0...v3.12.1

Jenkins pipeline link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!

[lemeurherve]

Build passed on all except one, merging.