feat: v2 mesh-init command

[DanStough]

Changes proposed in this PR:

• Add a new command mesh-init that replaces connect-init for V2 workloads. This uses the dataplane RPC to get the bootstrap config necessary for IPtables configuration. It also allows the workload time to reconcile in Consul before starting the rest of the pod.
• Removes the V2 flag from partition-init, since the V1 API will still work for this.
• Fixes the telemetry-collector for V2, which manually specifies these fields.

ACL Support is planned in the next release.

There is a follow-up task I will make to update all the connect-inject=truthy annotations in helm to also include mesh-inject.

How I've tested this PR: Unit/Integration tests with the Consul test server.

How I expect reviewers to test this PR: 👁️ 🔍

• I think it would help to go commit-by-commit since this PR has some separate concerns.
• I would compare this to the behavior of the connect-init command.
• I would also compare the telemetry V2 changes to the V1 YAML. The tests are identical, except for enabling V2.

Checklist:

• Tests added
• CHANGELOG entry added

[thisisnotashwin]

This looks great!! Nicely done!!

[zalimeni]

LGTM! Some minor comments but overall the adaptation of the existing command makes sense to me.

[DanStough]

I see the WANfed acceptance test failing in another commit on main, so I'm going to merge this.