Backport of Adding support for weighted k8s service into release/1.0.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #2293 to be assessed for backporting due to the inclusion of the label backport/1.0.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:
@srahul3
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: "21984e971d14125c96444283ad676e8837a925ab", automatic backport requires rebase workflow

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

---

Context

According to the documentation Consul supports setting weights for services . Unfortunately currently there is no way of doing that when using consul-k8s, as there is no annotation that can control that + there is no easy way of doing it via Consul API and it looks like the changes will be anyway overwritten.

Related link: https://hashicorp.atlassian.net/browse/NET-4266

Changes proposed in this PR:

• While the k8s syncs to consul, the LB service annotation consul.hashicorp.com/service-weight: <number> is read and then the weight is divided among underlying ingress/ips. The calculated weight is persisted as passing weight in consulapi.CatalogRegistration

How I've tested this PR:
Added the Junit test for different scenarios

How I expect reviewers to test this PR:

Checklist:

• Tests added
• CHANGELOG entry added

  HashiCorp engineers only, community PRs should not add a changelog entry.
  Entries should use present tense (e.g. Add support for...)

---

Overview of commits

• fdef617 - 7d47c00 - 552c0e7 - 14fa790 - 9f396c3 - 3320b62 - dc3e24e - 3dad9a0 - 95b3f7c - fa54600 - 21984e9 - 31c1506 - 9a25cbf