VAULT-32188: Enos test for PKI certificates

[tvo0813]

Description

VAULT-32188: Create Enos test for PKI issuing and signing certificates

TODO only if you're a HashiCorp employee

• Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
  • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
• ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
  of a public function, even if that change is in a CE file, double check that
  applying the patch for this PR to the ENT repo and running tests doesn't
  break any tests. Sometimes ENT only tests rely on public functions in CE
  files.
• Jira: If this change has an associated Jira, it's referenced either
  in the PR description, commit message, or branch name.
• RFC: If this change has an associated RFC, please link it in the description.
• ENT PR: If this change has an associated ENT PR, please link it in the
  description. Also, make sure the changelog is in this PR, not in your ENT PR.

[github-actions]

CI Results:
All Go tests succeeded! ✅

[github-actions]

Build Results:
All builds succeeded! ✅

[ryancragun]

Hot dang! Good job on your fist scenario expansion. Things are looking good!

It looks like we're missing updates to steps that are implemented by the vault_verify_secrets_engines_read module in a few scenarios:

• Autopilot
• DR Replication
• PR Replication
• Seal HA

We'll need to get those updates with the vault_root_token variable. It would be nice to create a test branch in vault-enterprise with all the changes to verify these changes so that when the CE -> Ent merge happens that there won't be any surprises.

While I didn't restate the feedback, the feedback on the read/pki module also applies to the create/pki module.