Upgrade consul to the latest major version
We are currently on consul 1.6.x, and upgrading to 1.7 includes some breaking changes that we will need to test out.
Consul recommends not being more than 2 major versions behind: https://www.consul.io/docs/upgrading#large-version-jumps so now that consul 1.9 has been released we should look at doing to work to perform the upgrade, either to 1.8 or to 1.9
The list of major changes that impact compatibility are documented in https://www.consul.io/docs/upgrading/upgrade-specific
In addition to testing the breaking changes, we don't automatically restart consul during reconfigure, so we will want to add additional messaging, as outlined in #2915 during the upgrade, instructing users to restart consul. Similar to what we do for postgres: https://gitlab.com/gitlab-org/omnibus-gitlab/-/blob/master/files/gitlab-cookbooks/postgresql/recipes/enable.rb#L154-165