appsec: Attacker Fingerprinting

[eliottness]

What does this PR do?

This PR finishing to setup Attacker fingerprinting:

• Support for server.business_logic.users.login.success address
• Support for server.business_logic.users.login.failure address
• Support for usr.session_id address
• Add all missing capabilities from the remoteconfig client
• Register fingerprinting capabilities at appsec start
• Upgrade the default ruleset to include fingerprinting preprocessors

System-tests job: https://github.com/DataDog/dd-trace-go/actions/runs/11127586022

Motivation

Implementation of the Attacker Fingerprinting RFC

Reviewer's Checklist

• Changed code has unit tests for its functionality at or near 100% coverage.
• System-Tests covering this feature have been added and enabled with the va.b.c-dev version tag.
• There is a benchmark for any new code, or changes to existing code.
• If this interacts with the agent in a new way, a system test has been added.
• Add an appropriate team label so this PR gets put in the right place for the release notes.
• Non-trivial go.mod changes, e.g. adding new modules, are reviewed by @DataDog/dd-trace-go-guild.

Unsure? Have a question? Request a review!

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-10-01 15:18:36

Comparing candidate commit 332a14d in PR branch eliott.bouhana/APPSEC-54278 with baseline commit daa6823 in branch main.

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

scenario:BenchmarkSampleWAFContext-24

• 🟥 execution_time [+4.399µs; +5.726µs] or [+2.425%; +3.157%]