[Fix] Consolidate CDK deployment into single command, add AWS deployment options to docs website and README

[kylehounslow]

Problem

The CDK Quick Start requires two separate npm install commands — one for the root and one for custom-resources/. These all serve the same goal (deploying AWS resources via CDK) and there is no technical reason for the split. Additionally, the root README has no mention of the AWS CLI installer or CDK deployment paths, and the docs website has no cloud deployment documentation.

Changes

CDK dependency consolidation:

• Merged custom-resources/package.json dependencies into root package.json
• Deleted custom-resources/package.json and package-lock.json
• Updated CDK README Quick Start: two install commands → one

The custom resource Lambdas use CDK's NodejsFunction with esbuild bundling. esbuild resolves imports via standard Node module resolution (walks up to root node_modules). The separate package.json was unnecessary.

Dependencies moved to root: @aws-crypto/sha256-js, @aws-sdk/credential-provider-node, @aws-sdk/signature-v4, @smithy/protocol-http.

Dependencies dropped: @aws-sdk/client-opensearch, @aws-sdk/client-secrets-manager — excluded via externalModules: ['@aws-sdk/*'] in all Lambdas that use them, provided by the Node.js 22 Lambda runtime.

Root README:

• Added Option 3: AWS Managed Services with component mapping table (local ↔ AWS managed equivalents)
• Added CLI installer and CDK subsections with quick start commands

Docs website (Starlight):

• Added new top-level "Deploy to Cloud" sidebar section between "Get Started" and "Send Data"
• docs/deploy/index.md — Overview page comparing Kubernetes vs Managed Services deployment paths, with component mapping table
• docs/deploy/aws.md — AWS Managed Services page with CLI installer and CDK instructions, SigV4 telemetry configuration, and cleanup commands
• Sidebar structured to grow for future native Kubernetes/Helm, Azure, and GCP docs

Testing

• cdk synth --all — all 4 Lambdas bundle successfully
• cdk deploy --all — full end-to-end deploy in us-west-2, all custom resources CREATE_COMPLETE
• cdk destroy --all — clean teardown
• Docs site builds with all internal links valid (105 pages)

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 18.51%. Comparing base (34475bd) to head (2852cf0).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #159   +/-   ##
=======================================
  Coverage   18.51%   18.51%           
=======================================
  Files           3        3           
  Lines          54       54           
  Branches       18       18           
=======================================
  Hits           10       10           
  Misses         44       44           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[joshuali925]

this sounds a bit generic, should title mention AWS? i don't think other cloud providers have all the services we use

[kylehounslow]

Good call out. I gave this some thought before landing on this structure. The idea is for "Deploy to Cloud" to be a top-level section that grows over time (short term: native Kubernetes/Helm, and eventually long-term: other cloud providers). I don't want to limit to AWS only. The sidebar already scopes it: the only child page is "AWS Managed Services", so users land in the right place. When we add Helm or another provider later we just drop a new page under the same section without restructuring.

[kylehounslow]

Despite not having all the services we use (mainly OSIS, AOS), an example of supporting other cloud providers could be native K8s / Helm but deployed on GKS or AKS.

[joshuali925]

nice