[DEBUG-3483] add: tests for probe budgets

[tylfin]

Motivation

This pull request includes several changes to the debugger tests and utilities, focusing on method refactoring, adding new test probes, and enhancing test coverage for probe budgets. The most important changes include adding new probe definitions, refactoring method calls, and updating test setup and validation logic.

Changes

• Added new probe definitions in tests/debugger/probes/probe_log_method_budgets.json and tests/debugger/probes/probe_snapshot_log_line_budgets.json to support logging and snapshot capturing for budget-related tests. [1] [2]
• Updated _setup method in tests/debugger/test_debugger_probe_snapshot.py to include timing logic and line probe setup.
• Added new test methods and validations for probe snapshots with budgets in tests/debugger/test_debugger_probe_snapshot.py.
• Introduced method_and_language_to_line_number in tests/debugger/utils.py to centralize line number mappings.
• Added a new endpoint /budgets/{loops} in utils/build/docker/java/spring-boot/src/main/java/com/datadoghq/system_tests/springboot/debugger/DebuggerController.java and utils/build/docker/python/flask/debugger_controller.py for budget-related tests. [1] [2]
• Introduced a new feature marker debugger_probe_budgets in utils/_features.py to manage probe budget tests.

Workflow

1. ⚠️ Create your PR as draft ⚠️
2. Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
3. Mark it as ready for review
   • Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
   • Framework is modified, or non obvious usage of it -> get a review from R&P team

🚀 Once your PR is reviewed, you can merge it!

🛟 #apm-shared-testing 🛟

Reviewer checklist

• If PR title starts with [<language>], double-check that only <language> is impacted by the change
• No system-tests internal is modified. Otherwise, I have the approval from R&P team
• CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
• A docker base image is modified?
  • the relevant build-XXX-image label is present
• A scenario is added (or removed)?
  • Get a review from R&P team

[tylfin]

@shurivich This is ready for review, there's some issues with the trigger probes for both Python and Java so that's currently disabled for all languages, but I'll re-enable when the problems are enabled. For now it gives us a rough idea that standard rate-limiting for enriched snapshots are working within a threshold.

[cbeauchesne]

Failing on CI (failure on java build step are not related, you can rebase your branch to fix them)

[shurivich]

LGTM with some small comments.