Backport of ci: pass required consul-k8s-workflows checks on CI skip into release/1.1.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #4144 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:
@zalimeni
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.

---

Unlike local job checks, these will not automatically be considered passing when skipped.

Follow-up to #4127 after enabling required checks for acceptance tests.

Changes proposed in this PR

• Skip newly required acceptance test checks (set by consul-k8s-workflows) when skipping CI due to docs-only changes

How I've tested this PR

#4146 (PR based on this branch, with skipping always on regardless of changed files, since this PR changes files that will not be skipped):

How I expect reviewers to test this PR

👀

Checklist

• Tests added
• CHANGELOG entry added

---

Overview of commits

• 3084407

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[zalimeni]

Closing in favor of #4205