Backport of when skip-ci is true do not trigger integration and go tests into release/1.15.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #18948 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:
@NiniOak
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: "a75f68f45012342e941f5b1a8941ce67074f0e60", automatic backport requires rebase workflow

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

---

Description

PROBLEM
Actions was not correctly reading the result of script to not run CI, it continuously ran CI when changes were only to docs file. See example here

SOLUTION
Push the result of script to GITHUB_OUTPUT which can be read easily by Github Actions to execute workflows conditionally.

Testing & Reproduction steps

CI runs all workflows where non doc files are included in changeset
CI skips test workflows when only doc files are in changeset

Links

PR Checklist

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

---

Overview of commits

• 89e15e4 - a75f68f - 80fcfd5

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

Auto approved Consul Bot automated PR