Replace all test private keys with dynamically-generated keys like //.hierarchy

[aarongable]

Twice in the last two weeks we have uploaded new private keys in PRs, and had to have SRE block those keys because they're compromised.

This should be impossible. We should make it so that boulder has no need for checked-in keys, by dynamically generating any such keys when the integration tests start. Then we should enable push protection with secret scanning to ensure that we never upload a private key to this repo ever again.

$ ag -l "BEGIN.*PRIVATE KEY"

• test/test-root2.key
• test/test-root.key
• test/hierarchy/*.key.pem
• test/grpc-creds/*/key.pem
• test/test-ee.key
• test/test-example.key
• test/mail-test-srv/localhost/key.pem
• test/mail-test-srv/minica-key.pem
• test/redis-tls/minica-key.pem
• test/redis-tls/boulder/key.pem
• test/redis-tls/boulder-redis/key.pem
• test/redis-tls/redis/key.pem
• test/wfe-tls/minica-key.pem
• test/wfe-tls/boulder/key.pem
• ca/testdata/ca_key.pem
• ca/testdata/testcsr.go
• cmd/ocsp-responder/testdata/test-ca.key
• grpc/creds/testdata/example.com/key.pem
• wfe2/test/238.key
• wfe2/test/178.key
• wfe2/wfe_test.go

$ find -type f -iname '*.der'

• //test/test-root.key.der
• //test/test-key-5.der
• //test/test-ca.key.der

[pgporada]

There's also some DER encoded private keys floating around such as the following. Note that public keys haven't been sorted out from this.

$ find -type f -iname '*.der'
./test/test-root.key.der
./test/test-ca.der
./test/test-key-5.der
./test/test-ca.key.der
./test/test-root.der

[aarongable]

test-ca.der and test-root.der are certificates; I've added the others to the checklist above.

[aarongable]

With #7488 out for review, only three clusters of keys remains:

• test-key-5 and the keys hardcoded into wfe_test.go, which correspond to pubkeys hardcoded into mocks/mocks.go and will therefore be a bit more complicated to remove
• the minica keys and certs for mail-test-srv, redis-tls, and wfe-tls, which can largely just be moved into the dynamically-generated PKI, except that some of them are used by unittests too
• //test/hierarchy, which we use nearly everywhere, and have been discussing replacing with a test-only package that generates such certs in-memory at init() time.