e2e: Ensure Consul client is running before starting Nomad service.

[jrasell]

The recent change of the Consul fingerprinter means Consul must be up and started before the Nomad client, otherwise the Nomad process needs to be sent a SIGHUP.

Contributor Checklist

• Changelog Entry If this PR changes user-facing behavior, please generate and add a
  changelog entry using the make cl command.
• Testing Please add tests to cover any new functionality or to demonstrate bug fixes and
  ensure regressions will be caught.
• Documentation If the change impacts user-facing functionality such as the CLI, API, UI,
  and job configuration, please update the Nomad website documentation to reflect this. Refer to
  the website README for docs guidelines. Please also consider whether the
  change requires notes within the upgrade guide.

Reviewer Checklist

• Backport Labels Please add the correct backport labels as described by the internal
  backporting document.
• Commit Type Ensure the correct merge method is selected which should be "squash and merge"
  in the majority of situations. The main exceptions are long-lived feature branches or merges where
  history should be preserved.
• Enterprise PRs If this is an enterprise only PR, please add any required changelog entry
  within the public repository.

[tgross]

It looks like as of hashicorp/consul#16845 Consul supports systemd Type=notify and that's actually now part of their packaged unit file: https://github.com/hashicorp/consul/blob/main/.release/linux/package/usr/lib/systemd/system/consul.service#L9 We're not using that unit file (for reasons which were probably good at the time but may not make sense anymore). That should allow depends/wants to work correctly.

[tgross]

LGTM!