docs: add AWS Workload Identity Federation integration guide

[girish-cheedala]

• Add Workload Identity Federation (WIF) as a fourth AWS integration method, marked as recommended
• Document step-by-step setup: OIDC provider creation, WIF role, scanner role, and optional org-level discovery
• Highlight security benefits (no long-lived credentials, short-lived tokens, CloudTrail audit trail)
• Update introduction to reference four connection methods instead of three

[neo-by-projectdiscovery-dev]

Neo - PR Security Review

No security issues found

Highlights

• Adds AWS Workload Identity Federation (WIF) as recommended fourth integration method
• Documents step-by-step OIDC provider setup with properly scoped trust policies using Team ID constraints
• Implements role separation pattern: WIF role for trust boundary, separate scanner roles for resource permissions
• Includes optional organization-level discovery for automatic multi-account enumeration

Hardening Notes

• Consider adding guidance to enable CloudTrail logging for the scanner role assumptions to track all federated access
• Add a note recommending customers periodically review which accounts have PDScannerRole deployed to detect unauthorized role creation
• Consider documenting how to add resource-based policies (e.g., S3 bucket policies) as defense-in-depth to prevent even read-only roles from accessing highly sensitive resources

_{Comment @pdneo help for available commands. · Open in Neo}