Backport of Update Release Scripts into release/1.1.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #2558 to be assessed for backporting due to the inclusion of the label backport/1.1.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:
@wilkermichael
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.

---

NOTE TO REVIEWER: You can go through my PR commit by commit, I've organized changes to be isolated to each commit. You can often get more context from them.

Changes proposed in this PR:

• update environment variables with CONSUL_K8s prefix. This will let us check that we have all the environment variables set more easily with printenv | grep "CONSUL_K8S"
• also added a make target that just runs printenv | grep "CONSUL_K8S"
• update imageConsulDataplane without quotes. This makes it consistent with the other images and allows scripting to work similarly to other images
• updated utils script
  • handle replace case where consul-enterprise is in the values.yaml file and charts.yaml file
  • handle adding pre-release tag in changelog
  • handle updating consul-dataplane

How I've tested this PR:

• Ran three scenarios for prepare release/prepare dev scripts

1. Scenario with a prerelease set (rc1)
2. Scenario with switching to dev mode
3. Scenario with release without a prerelease set

• ran make check-env

$ make check-env      
CONSUL_K8S_RELEASE_BRANCH=release/1.1.0
CONSUL_K8S_PRERELEASE_VERSION=
CONSUL_K8S_CONSUL_VERSION=1.16.0
CONSUL_K8S_CONSUL_DATAPLANE_VERSION=1.2.0
CONSUL_K8S_RELEASE_DATE=September 31, 2022
CONSUL_K8S_NEXT_CONSUL_DATAPLANE_VERSION=1.1.3
CONSUL_K8S_PRODUCT_VERSION=1.1.0
CONSUL_K8S_NEXT_CONSUL_VERSION=1.17.3
CONSUL_K8S_NEXT_RELEASE_VERSION=1.1.6
CONSUL_K8S_RELEASE_VERSION=1.1.0
CONSUL_K8S_LAST_RELEASE_GIT_TAG=v0.48.0

How I expect reviewers to test this PR:

• I've included the outputs of each scenario in my testing as commits that I'll drop, so check out those commits
• 👀

Checklist:

• Tests added
• CHANGELOG entry added

---

Overview of commits

• 64a1679 - 064e05a - 1536ff7 - e3b4e50