Add TemporaryRequestContext unit tests

[claponcet]

What Does This Do

Adds unit tests for the TemporaryRequestContext private static class inside LambdaAppSecHandler, covering:

• getData() returns the stored AppSec context for the APPSEC slot and null for other slots
• All no-op methods (getTraceSegment, getBlockResponseFunction, getOrCreateMetaStructTop, getClientIpAddressData, setters, close) return expected defaults and do not throw

Since TemporaryRequestContext is private, tests capture an instance by intercepting the requestMethodUriRaw callback during a processRequestStart invocation with a mocked tracer.

Motivation

Improve test coverage for TemporaryRequestContext.

Additional Notes

tag: no release note

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Add your completed PR to the merge queue by commenting /merge.

Jira ticket: [PROJ-IDENT]

[jandro996]

nit: consider also testing a slot beyond CI_VISIBILITY (e.g. IAST) and the edge case where appSecContext is null — in that case getData(APPSEC) should also return null, which is currently not covered.

[jandro996]

nit: throws Exception is unnecessary here — none of the no-op methods actually throw a checked exception. The comment "verify no-op methods don't throw" makes the intent clear, but the throws clause sends the opposite signal. Removing it makes the method signature self-documenting.

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.85 s	14.68 s	[+0.4%; +2.0%] (maybe worse)
startup:insecure-bank:tracing:Agent	13.60 s	13.72 s	[-1.7%; +0.1%] (no difference)
startup:petclinic:appsec:Agent	16.82 s	16.76 s	[-0.6%; +1.4%] (no difference)
startup:petclinic:iast:Agent	16.31 s	16.90 s	[-7.8%; +0.9%] (no difference)
startup:petclinic:profiling:Agent	16.82 s	16.87 s	[-1.5%; +0.9%] (no difference)
startup:petclinic:sca:Agent	16.87 s	16.62 s	[+0.6%; +2.5%] (maybe worse)
startup:petclinic:tracing:Agent	16.02 s	15.56 s	[-1.4%; +7.3%] (no difference)

Commit:a25135a7 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[jandro996]

LGTM! just minor comments

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-06-30 08:55:00 UTC ℹ️ Start processing command /merge

---

2026-06-30 08:55:05 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 2h (p90).

---

2026-06-30 09:54:53 UTC ℹ️ MergeQueue: This merge request was merged