e2e: provision Consul with ACLs enabled

[shoenig]

As part of #6701, we'd like to have some e2e testing around making use of Nomad's Consul Connect integration with Consul ACLs enabled.

Currently, the e2e test suite provisions Consul without ACLs enabled, and there isn't yet a great way to re-configure services once provisioned. A workaround could be to just change the terraform provisioning steps such that Consul is always initially provisioned with ACLs enabled. In theory no existing tests should break, and this will enable testing against the ACL features. Initializing with ACLs enabled has the side benefit of being simpler to disable later on, rather than trying to activate ACLs on an already initialized Consul cluster

[github-actions]

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.