chore: update algoliasearch latest version to 4.11.2

[github-actions]

Update algoliasearch lockfiles and dependency package lockfiles.
This performs the following updates:

1. Some algoliasearch lockfiles use algoliasearch latest. This will update algoliasearch and dependencies.
2. Some algoliasearch lockfiles use a pinned (non-latest) version of algoliasearch, but require the latest version of another package. This will update all such packages.

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

[pr-commenter]

Benchmarks

Benchmark execution time: 2025-01-06 18:05:29

Comparing candidate commit c731cef in PR branch upgrade-latest-algoliasearch-version with baseline commit 6bfe77e in branch main.

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

scenario:iast_aspects-replace_aspect

• 🟥 execution_time [+594.232ns; +677.435ns] or [+8.845%; +10.084%]

[github-actions]

CODEOWNERS have been resolved as:

.riot/requirements/14be2f6.txt                                          @DataDog/apm-python
.riot/requirements/1a06ac7.txt                                          @DataDog/apm-python
.riot/requirements/1b0d918.txt                                          @DataDog/apm-python
.riot/requirements/1ccf91d.txt                                          @DataDog/apm-python
.riot/requirements/404933a.txt                                          @DataDog/apm-python
.riot/requirements/b80e42b.txt                                          @DataDog/apm-python
.riot/requirements/cc2f3f8.txt                                          @DataDog/apm-python
.riot/requirements/e1220d6.txt                                          @DataDog/apm-python
.riot/requirements/feaf737.txt                                          @DataDog/apm-python

[mabdinur]

This PR doesn't actually update algoliasearch to 4.11.2. It just bumps some transitive dependencies. There is likely a bug in the script.

cc: @quinna-h @bouwkast

[bouwkast]

You're correct algoliasearch is a pinned package for dd-trace-py and shouldn't be updated.

@quinna-h I see the workflow outputting the following as updateable:

algoliasearch botocore starlette coverage tornado aiohttp falcon anthropic logbook pynamodb langchain urllib3 dramatiq jinja2 django protobuf flask aiobotocore openai

Maybe something wrong going on in here?

dd-trace-py/scripts/freshvenvs.py

Line 201 in 81208cd

def _venv_sets_latest_for_package(venv: riotfile.Venv, suite_name: str) -> bool:

[bouwkast]

dd-trace-py/scripts/freshvenvs.py

Line 126 in 81208cd

packages = {m for m in modules if "." not in m}

Needs to check for the pinned versions
->

packages = {m for m in modules if "." not in m and m not in pinned_packages}

[quinna-h]

#11864 - the logic in #11372 accidentally removed this check.

[mabdinur]

Changes don't match the PR title

[quinna-h]

Fix #11868 was merged - this PR should not have been generated in the first place (and will not be in the future). Closing the PR.