build(deps): bump abseil-cpp from 20260526.0 to 20260817.0 in the bazel-packages group

[dependabot]

Bumps the bazel-packages group with 1 update: abseil-cpp.

Updates abseil-cpp from 20260526.0 to 20260817.0

Release notes

Sourced from abseil-cpp's releases.

Abseil LTS branch, August 2026

Abseil LTS 20260817.0

What's New

• Added URL escaping utilities
• Many bug fixes and optimizations

Breaking Changes

• absl::void_t is now deprecated; users should use C++17 std::void_t directly.
• Hashtable iterators returned from insert/emplace are now non-iterable (any prior use of iteration was likely a bug).

Known Issues

• None at this time

Baseline: 2065f4ded0558c6f89fee67c8e5228feb4eb960e

Commits

• 2065f4d Apply LTS transformations for 20260817 LTS branch (#2129)
• 060c916 cord_internal: fix a clang-tidy complaint about implicit bool conversions.
• 7e70692 Internal cleanup
• c92db17 Rollback Merge CRC+memcpy functionality into Extend function
• 9655f54 Merge CRC+memcpy functionality into Extend function.
• 0cd1562 Update dependencies in preparation for release
• 3b49be4 Add more bits to size by reducing size of capacity and seed.
• ba427a3 Remove unused includes from absl/hash/hash.h and `absl/hash/internal/hash.h...
• 0042850 Remove asan instrumentation in some test code to prevent re-entrancy deadlock...
• 5b1163c Remove unused includes from absl/hash/hash.h and `absl/hash/internal/hash.h...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-09-01 19:36:21

Comparing candidate commit 286d738 in PR branch dependabot/bazel/bazel-packages-eaadbf79a8 with baseline commit 83cbde0 in branch main.

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

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'