[CI Visibility] Initial internal consts and utilities

[tonyredondo]

What does this PR do?

This PR introduces the CI Visibility product in the repository with the following initial code:

• Constants: constants used by the product on their integrations, most of the constants have a significant value at backend side.
• Utilities: the utils packages contains base an utilities functions to:
  • Extract CI Providers data.
  • Extract the CODEOWNERS file information
  • Extract Git information
  • Expand the HOME "~" char.
  • Other small utilities.

Coverage is in the 94.2%

❯ go test ./... -cover   
?       gopkg.in/DataDog/dd-trace-go.v1/internal/civisibility/constants [no test files]
ok      gopkg.in/DataDog/dd-trace-go.v1/internal/civisibility/utils     0.495s  coverage: 94.2% of statements

Motivation

We are working on adding Go as a supported language on the CI Visibility product.

This is the first PR of an stacked series.

More info is available in the guild slack channel.

Stacked PRs

1. [CI Visibility] Initial internal consts and utilities #2736 | [This one]
2. [CI Visibility] Add support for CI Visibility mode in ddtrace #2739
3. [CI Visibility] Manual Api and Go/Testing integration #2742

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.

Unsure? Have a question? Request a review!

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-07-08 09:54:59

Comparing candidate commit 1aba968 in PR branch tony/civisibility-part1-consts-and-utils with baseline commit 79237af in branch tony/civisibility-ddtrace.

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

scenario:BenchmarkHttpServeTrace-24

• 🟩 execution_time [-769.877ns; -659.923ns] or [-4.447%; -3.812%]

[Julio-Guerra]

Looks good overall.

You forgot to review all our .github workflows to search for internal/ and add internal/civisibility too to some of the go test commands we built-in there (we can't do go test ./... due to some contribs which require more or are incompatible between them)

[tonyredondo]

Looks good overall.

You forgot to review all our .github workflows to search for internal/ and add internal/civisibility too to some of the go test commands we built-in there (we can't do go test ./... due to some contribs which require more or are incompatible between them)

As talked offline, civisibility tests are running without any workflow modification.

[ManuelPalenzuelaDD]

LGTM

[darccio]