ci: update which packages to select for update

[quinna-h]

Skip over pinned modules when checking for outdated packages.

Since the modules are pinned, we won't actually update the latest that we use from the riotfile, so it is not necessary to include them in the list of candidates for updating a package version.

Future items:

• Figure out a more robust solution for mapping the suite name to the integration name (currently hardcoded in a dict)

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:

scripts/freshvenvs.py                                                   @DataDog/apm-core-python

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-09-24 02:52:41

Comparing candidate commit 1293ddd in PR branch quinna.halim/update-package-logic with baseline commit cf6f007 in branch main.

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

[emmettbutler]

If I understand this series of workflows properly, this line in freshvenvs.py is the original source of the list of packages that might need updates. Instead of setting up another workflow and committing another text file to source control, I think it's possible to achieve the goal of avoiding updates for certain packages by putting the update_pinned.py logic directly in the freshvenvs script.

[quinna-h]

If I understand this series of workflows properly, this line in freshvenvs.py is the original source of the list of packages that might need updates. Instead of setting up another workflow and committing another text file to source control, I think it's possible to achieve the goal of avoiding updates for certain packages by putting the update_pinned.py logic directly in the freshvenvs script.

Addressed! A concern I had was how frequently are we running scripts/freshvenvs vs updating the riotfile (the thought being that parsing through all the Venvs in riotfile is time consuming), but on second thought doing this once a week is fine.

[emmettbutler]

This is looking great. I left a bunch of comments about clarity and readability, plus one that appears to be a logical error. Let me know when you'd like another review!