ci: move the pygoat test to gitlab and hatch and make it faster

[juanjux]

Description

• Moves from riot + CircleCI to hatch + gitlab.
• Remove the docker stuff.
• Faster: from 10-12 minutes to 5-7.

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[github-actions]

CODEOWNERS have been resolved as:

.riot/requirements/363e03d.txt                                          @DataDog/apm-python
.riot/requirements/e768555.txt                                          @DataDog/apm-python
tests/appsec/integrations/pygoat_tests/fixtures/pygoat.xz               @DataDog/asm-python
tests/appsec/integrations/pygoat_tests/fixtures/remake_pygoat_fixture.sh  @DataDog/asm-python
tests/appsec/integrations/pygoat_tests/run_pygoat.sh                    @DataDog/asm-python
.circleci/config.templ.yml                                              @DataDog/python-guild @DataDog/apm-core-python
.gitignore                                                              @DataDog/apm-core-python
docker-compose.yml                                                      @DataDog/apm-core-python
hatch.toml                                                              @DataDog/python-guild
lib-injection/sources/min_compatible_versions.csv                       @DataDog/apm-core-python
min_compatible_versions.csv                                             @DataDog/apm-core-python
riotfile.py                                                             @DataDog/apm-python
tests/appsec/integrations/pygoat_tests/test_pygoat.py                   @DataDog/asm-python
tests/appsec/suitespec.yml                                              @DataDog/asm-python
tests/internal/test_auto.py                                             @DataDog/apm-core-python
.riot/requirements/285d807.txt                                          @DataDog/apm-python

[github-actions]

Bootstrap import analysis

Comparison of import times between this PR and base.

Summary

The average import time from this PR is: 230 ± 2 ms.

The average import time from base is: 230 ± 2 ms.

The import time difference between this PR and base is: -0.2 ± 0.1 ms.

The difference is not statistically significant (z = -1.85).

Import time breakdown

The following import paths have shrunk:

ddtrace.auto 1.742 ms (0.76%)

ddtrace.bootstrap.sitecustomize 1.163 ms (0.51%)

ddtrace.bootstrap.preload 1.163 ms (0.51%)

ddtrace.internal.products 1.163 ms (0.51%)

ddtrace.internal.remoteconfig.client 0.617 ms (0.27%)

ddtrace 0.579 ms (0.25%)

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-04-02 10:24:23

Comparing candidate commit 465d51b in PR branch juanjux/move-pygoat-test-to-gitlab with baseline commit dc10e19 in branch main.

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

[avara1986]

LGTM! thank you for migrate this appsec test. I love this smart approach without docker, congrats!

[github-actions]

The backport to 2.21 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.21 2.21
# Navigate to the new working tree
cd .worktrees/backport-2.21
# Create a new branch
git switch --create backport-13002-to-2.21
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 5b3a8f23a3af8d96666cff11bfda0d4a573df30a
# Push it to GitHub
git push --set-upstream origin backport-13002-to-2.21
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.21

Then, create a pull request where the base branch is 2.21 and the compare/head branch is backport-13002-to-2.21.

[github-actions]

The backport to 3.1 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-3.1 3.1
# Navigate to the new working tree
cd .worktrees/backport-3.1
# Create a new branch
git switch --create backport-13002-to-3.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 5b3a8f23a3af8d96666cff11bfda0d4a573df30a
# Push it to GitHub
git push --set-upstream origin backport-13002-to-3.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-3.1

Then, create a pull request where the base branch is 3.1 and the compare/head branch is backport-13002-to-3.1.

[github-actions]

The backport to 3.2 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-3.2 3.2
# Navigate to the new working tree
cd .worktrees/backport-3.2
# Create a new branch
git switch --create backport-13002-to-3.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 5b3a8f23a3af8d96666cff11bfda0d4a573df30a
# Push it to GitHub
git push --set-upstream origin backport-13002-to-3.2
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-3.2

Then, create a pull request where the base branch is 3.2 and the compare/head branch is backport-13002-to-3.2.