[Schedule merge 19.12] Feature/use aws

[hieu-aiven]

What changed

• Migrate search & feedback functions away from Netlify and into AWS Lambda
• Remove runtime.txt that define the Python version to use during runtime and set it as environment variable in the deployment platform instead to ensure the site works in both Netlify and Cloudflare Pages during the transition period for DNS update. This is because Netlify requires Python 3.8 while Cloudflare Pages requires Python 3.7.

Why

• Eliminate deployment platform dependency for search & feedback function
• Better development workflow as 2 functions can now be tested locally with AWS SAM.
• Reduce platform cost as Netlify pricing based on user and Git contributors doesn't scale with Open source project like DevPortal.

Process for the switch Netlify to Cloudflare Pages

• Function deployment to production with Aiven AWS account. Pending access
• Approve PR feature/use-aws and merge to main
• Update Cloudflare Pages production build from branch feature/use-aws to main
• Update DNS CNAME pointing to CP so the docs.aiven.io will serve from CP → SRE-5211

Switch completed

[Ugbot]

added two comments around default postrgess ports vs passing them and an env variable,
also around the PG insert, From what ive seen around Aiven, this should be using a PG function not a direct query. Neither of these are blocking issues assuming you've tested the PG stuff, and are sure around Aiven Dev policy on PG functions vs queries.