HVT-6147: Fix and enable vault acceptance tests

[chirags101]

Enabling failing tests TestAcc_Vault_ClusterAWS and TestAcc_Vault_PerformanceReplication_ValidationsAws

TestAcc_Vault_ClusterAWS encountered failures while updating the cluster tier and public/proxy settings. During the upgrade, only the cluster tier was updated, while the publicIP/proxy configuration remained was not updated (admin/UI and update cadence WF input as well) which seems like a potential bug or missout.

TestAcc_Vault_PerformanceReplication_ValidationsAws :

• The hcpv-observability-http LD flag was enabled for the integration environment to allow HTTP audit log streaming.
• Resource validation for audit_log_config was failing which was fixed by doing indentation for audit_log_config set for resource
• In one of the test steps, the cluster configuration was changed from DEV to PLUS_SMALL, which is not permitted in the cloud-vault-service; it has now been updated to STANDARD_SMALL.

Jira: https://hashicorp.atlassian.net/browse/HVT-6147

Jira to track publicIP/proxy + tier modification bug: https://hashicorp.atlassian.net/browse/HVT-6463

🛠️ Description

🏗️ Acceptance tests

• Are there any feature flags that are required to use this functionality?
• Have you added an acceptance test for the functionality being added?
• Have you run the acceptance tests on this branch?

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccXXX'

...

[hashicorp-cla-app]

All committers have signed the CLA.

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[jasonpilz]

Awesome, thanks a ton for doing this!