fix(.github/workflows): add tags-ignore to avoid running CI on pushing tags for contribs and other nested modules

[darccio]

What does this PR do?

Adding tags-ignore to all GitHub Actions' workflows so they don't run when pushing tags.

Motivation

dd-trace-go@v2 has 50+ tags per release, so pushing them generate a lot of workload in CI.

Reviewer's Checklist

• Changed code has unit tests for its functionality at or near 100% coverage.
• System-Tests covering this feature have been added and enabled with the va.b.c-dev version tag.
• There is a benchmark for any new code, or changes to existing code.
• If this interacts with the agent in a new way, a system test has been added.
• Add an appropriate team label so this PR gets put in the right place for the release notes.
• Non-trivial go.mod changes, e.g. adding new modules, are reviewed by @DataDog/dd-trace-go-guild.
• For internal contributors, a matching PR should be created to the v2-dev branch and reviewed by @DataDog/apm-go.

Unsure? Have a question? Request a review!

[nsrip-dd]

dd-trace-go@v2 has 50+ tags per release, so pushing them generate a lot of workload in CI.

If I understand correctly, this is because there will be seperate modules for each contrib/integration, which we need to tag seperately? But the tags will all point to the same code, right? If so, definitely makes sense not to run redundant CI on those tags.

[hannahkm]

So these checks would still run on all PRs, but not for each pushed tag, right?

[darccio]

Exactly.

[datadog-datadog-prod-us1]

Datadog Report

Branch report: dario.castane/ignore-tags-on-push
Commit report: 0b28f10
Test service: dd-trace-go

✅ 0 Failed, 5094 Passed, 67 Skipped, 2m 29.74s Total Time

[darccio]

If I understand correctly, this is because there will be seperate modules for each contrib/integration, which we need to tag seperately? But the tags will all point to the same code, right? If so, definitely makes sense not to run redundant CI on those tags.

Indeed, @nsrip-dd, this is the case. Although the process involves tagging and pushing tags in three phases (1, tag the root module; 2, tag contribs that are imported by other contribs; 3, tagging the rest of modules), they are the same code altogether (replace directives override the version set in each go.mod).

Also, all the code is already tested in the PRs, nightlies, etc.

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-12-04 16:12:20

Comparing candidate commit 74620b4 in PR branch dario.castane/ignore-tags-on-push with baseline commit 076462a in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 58 metrics, 1 unstable metrics.