Backport of remove all k8s services from consul into release/1.3.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #4255 to be assessed for backporting due to the inclusion of the label backport/1.3.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@wangxinyi7
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul-k8s/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

Changes proposed in this PR

• Support removing the registered K8S services from consul when user runs consul sync-catalog -purge-k8s-services-from-node=k8s-sync.

How I've tested this PR

1. Start with disabling syncCatalog
2. Enabling syncCatalog: Confirmed from Consul UI that K8S services registered in Consul
3. Disabling syncCatalog: registered services still in the dashboard
4. Run consul sync-catalog -purge-k8s-services-from-node=k8s-sync
5. Confirmed from Consul UI that registered K8S services are de-registered in Consul

How I expect reviewers to test this PR

Checklist

• Tests added
• CHANGELOG entry added

---

Overview of commits

• 0c5150d - e3b74dd - 0a9a7cb - a211357 - 45381f9 - e5061e4 - 27b4eb9 - 82ff2a9 - 379a6b3 - 7e26d8c - f69c0f3 - f7a8cf6 - e44042a

[hashicorp-cla-app]

All committers have signed the CLA.