Backport of Bugfix: Don't recreate servicemap for catalog sync into release/1.4.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #3785 to be assessed for backporting due to the inclusion of the label backport/1.4.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:
@jmurret
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: unable to process merge commit: "c1921966841cdef99078e40c355470ac8aeb4b85", automatic backport requires rebase workflow

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

---

Changes proposed in this PR

• I recently contributed Catalog: Use EndpointSlice and propagate Kubernetes Topology information to synced consul service #3693 only to discover a bug that will add every service to the serviceMap and trigger a registration in consul. This removes that bug.

How I've tested this PR

Existing tests and a manual build/deploy in my environment to confirm we don't register everything

How I expect reviewers to test this PR

With my previous change, if spinning up consul catalog sync you'll see every k8s service become registered regardless of configuration. With this change you should only see intended services become registered.

Checklist

• Tests added
• CHANGELOG entry added

---

Overview of commits

• 5208e7b - c192196