Backport of Removed nodename and status from consul snapshot save -append-filename command and using leader version in version into release/1.15.x

[hc-github-team-consul-core]

Backport

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

🚨

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:
@absolutelightning
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: "5353c807068363848db0c506db9ea2a014f54f8e", automatic backport requires rebase workflow

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

---

Description

Using leader version in version. Also removes nodename and status in consul snapshot save -append-filename command

Testing & Reproduction steps

make dev
./bin/consul agent -dev -config-file=../server.json
./bin/consul snapshot save -append-filename version,dc snap.bkp

asheshvidyut@asheshvidyut-H2GX766V9T ~/consul (fix-snapshot-save-append-file %) » ./bin/consul snapshot save -append-filename version,dc snap.bkp                                        130 ↵
Saved and verified snapshot to index 17
asheshvidyut@asheshvidyut-H2GX766V9T ~/consul (fix-snapshot-save-append-file %) » ls | grep snap-1.17.0-dc1.bkp
snap-1.17.0-dc1.bkp

Links

PR Checklist

• updated test coverage
• external facing docs updated
• appropriate backport labels added
• not a security concern

---

Overview of commits

• e8f4bfe - 5072958 - 5353c80 - 0bc54b1 - 2f74f08 - fc4fd36 - e31cca3 - f00f303 - e063cd2

[github-team-consul-core-pr-approver]

Auto approved Consul Bot automated PR

[hc-github-team-consul-core]

🤔 This PR has changes in the website/ directory but does not have a type/docs-cherrypick label. If the changes are for the next version, this can be ignored. If they are updates to current docs, attach the label to auto cherrypick to the stable-website branch after merging.