Add takeaways on json and maps to test migration skill

[amarziali]

What Does This Do

Improves the migration skill with instructions on:

• json assertions (using json-junit-assert)
• Map translations from groovy

Motivation

Additional Notes

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. You can also:
  • Customize the commit message associated with the merge with /merge --commit-message "..."
  • Remove your PR from the merge queue with /merge -c
  • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
  • Get more information in this doc

Jira ticket: [PROJ-IDENT]

[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.03 s	13.98 s	[-0.9%; +1.7%] (no difference)
startup:insecure-bank:tracing:Agent	12.84 s	12.98 s	[-2.0%; -0.3%] (maybe better)
startup:petclinic:appsec:Agent	16.46 s	15.47 s	[-2.7%; +15.6%] (unstable)
startup:petclinic:iast:Agent	16.60 s	16.66 s	[-2.0%; +1.3%] (no difference)
startup:petclinic:profiling:Agent	16.49 s	16.58 s	[-2.2%; +1.0%] (no difference)
startup:petclinic:tracing:Agent	15.93 s	15.94 s	[-1.8%; +1.6%] (no difference)

Commit: a5f95093 · 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.