CM-798, CM-799: Migrate e2e tests for ACME issuer from private suite

[lunarwhite]

Tracked by https://issues.redhat.com/browse/CM-798, https://issues.redhat.com/browse/CM-799

Main changes

Divides the single test/e2e/certificates_test.go file into separate suites/files to maintain readability as the tests grow.

Adds new test cases in test/e2e/issuer_acme_http01_test.go (labeled TechPreview)

• ACME Issuer HTTP01 solver with Certificate object should select appropriate solver based on selector configuration
• ACME Issuer HTTP01 solver with Certificate object should obtain a valid certificate in HTTPS proxy with trusted CA

Adds new test cases in test/e2e/issuer_acme_dns01_test.go (labeled TechPreview)

• ACME Issuer DNS01 solver with AWS Route53 should obtain a valid certificate when no hosted zone overlap
• ACME Issuer DNS01 solver with AWS Route53 should obtain a valid certificate with DNS-over-HTTPS
• ACME Issuer DNS01 solver with AWS Route53 in STS environment should obtain a valid certificate using ambient credentials through pod-identity-webhook
• ACME Issuer DNS01 solver with AWS Route53 in STS environment should obtain a valid certificate using ambient credentials through manually patched secret
• ACME Issuer DNS01 solver with Google CloudDNS in Workload Identity environment should obtain a valid certificate using ambient credentials

Adds a new label category CredentialsMode to indicate authentication methods with cloud platforms (i.e. DNS01 providers), updates default E2E_GINKGO_LABEL_FILTER to exclude Manual which would require STS/WIF setup

• Manual: suitable for the AWS STS or GCP/Azure WIF cluster
• Mint: suitable for the normal standalone cluster