Provider Key: SAP-cloud-infrastructure/sci

[github-actions]

Updated .//keys/s/sap-cloud-infrastructure/sci/provider-1750415142.asc for provider sap-cloud-infrastructure. Closes #2322.

[Yantrio]

@kayrus before this is merged, I just wanted to check that this is the correct key you wanted to upload :)

[kayrus]

@Yantrio Yes, I ran into issues with Terraform HCP: Could not verify the signature of the checksum file: SHASUM signature failed verification: Invalid signature.

It was very similar to this problem.
The issue only occurred on HCP, so I had to release the namespace there and then claim it again on the regular Terraform Registry. That worked smoothly.

The downside is that I had to recreate the GPG RSA key multiple times with different parameters, before I found a solution, which led to the current mess.

[kayrus]

@Yantrio already existing key is an ed25519 key. It's also not supported by Hashicorp, but it works fine with opentofu. Is it ok to have two keys? Or do we need to remove an old one?

UPD: it looks like some providers have 5 keys. Therefore, I suppose it won't be a problem.

      2 keys/d/datadog/datadog
      2 keys/l/launchdarkly/launchdarkly
      2 keys/m/maxlaverse
      2 keys/p/pixarv
      2 keys/s/spacelift
      2 keys/t/terraform
      3 keys/c/ciscodevnet/cml2
      5 keys/c/cofide/cofide

[Yantrio]

Sure it's okay to have multiple keys 👍