Integrate verified privesc v4 catalog fragments (AWS/GCP/Azure/K8s)

[carlospolop]

Verified privesc v4 catalog integration

The 17 integration commits add reviewed, evidence-bound catalog entries for defensive detection across AWS, GCP, Azure, Kubernetes, and related platform sources. Missing collector facts leave conditional techniques UNKNOWN. Rejected proposals were not added; schema and collector requests remain documented for later work.

Per-provider counts from the v4int-*.md integration reports:

Provider	Entries added	Exclusions added	Fixed	Collector UNKNOWN / requests	Rejected
AWS	126	200	337	119	315
GCP	63	72	124	60	149
Azure	42	77	109	42	71
Kubernetes and other sources	3	185	8	3	74

Counts sum the report categories; collector counts can overlap entries and fixes. The AWS collector count includes 25 queued requests in v4int-aws-04.md, some of which accompany fixes rather than new entries. Entries added includes collector-gated entries and three AWS replacement entries. Rejected counts include verifier rejections and the integration rejections identified in the reports.

Validation after rebasing onto origin/master: python3 scripts/validate_privesc_paths.py reported 0 errors across 283 files, 1,210 techniques, and 3,353 reviewed exclusions.

🤖 Generated with Codex