docs(collector): fix AWS CUR console steps and manual IAM role policy

[saiprasadpotdar]

Summary

Two parts of the AWS page no longer matched the console or the product:

• Creating a CUR pointed at a Cost & Usage Reports page and a Legacy CUR (CUR 1.0) option that no longer exist. The console now creates legacy reports under Data Exports → Create → Export type: Legacy CUR export. Steps rewritten to the current screen and the missing Include resource IDs checkbox added (the CloudFormation template sets it; without it per-resource cost is empty).
• Least-Privilege IAM Policy (Manual Role Creation) listed 13 actions across four services, while the CloudFormation role attaches ReadOnlyAccess plus billing and Logs rights and the collector calls ~50 services. A role built from the old policy authenticated and read CUR but failed discovery for EC2, RDS, Lambda, ECS and everything else with AccessDenied. It also gave no trust policy and did not say that Standard access mode needs write actions the doc never listed. The section now has: a trust policy with where to find NudgeBee's principal ARN; Option A mirroring the template (ReadOnlyAccess + inline billing/logs/CUR); Option B, an explicit least-privilege policy derived from every SDK call in collector-server/cloud-collector/providers/aws; and a table of Standard-mode write actions.

Also tightened the Method 2 sentence, which put sts:AssumeRole in the permissions policy instead of the trust policy.

Type of change

• Update to existing documentation

Verification

• CUR steps checked against the AWS user guide, Creating a Legacy CUR export.
• Option A copied from nudgebee-aws-cloud-formation.json (read-only branch). Option B generated from a sweep of <service>.<Method>Input calls in the collector, api-server crawl and llm-server cloud tools, mapped to IAM action names.
• Reviewer check: open the AWS console → Billing and Cost Management → Data Exports → Create and confirm the labels in the steps match.

Checklist

• I ran npm run build locally and the site builds without errors
• I ran npm run lint locally and lint passes (lint targets .tsx only; no TSX changed)
• Internal links work; new external links open the correct page
• My commits are signed off (DCO — git commit -s)
• I read CONTRIBUTING.md

[gemini-code-assist]

Code Review

This pull request updates the AWS integration documentation to align with the latest AWS Console UI for Data Exports and expands the manual IAM role creation guide with detailed trust and permissions policies. The review feedback recommends updating a button label to match the verbatim AWS UI and replacing the retired aws-portal:View* permission with the modern billing:View* equivalent.