docs: Add a guide for running airbyte workloads on custom nodes

[chrishronek]

Summary

If your customers want to run Airbyte workloads on a specific node type, this should get them started.

Test Plan

I'm using the documented configuration on my plural.sh hosted Airbyte and it's working great.

Checklist

• No images hosted from dockerhub
• Are dashboards present to understand the health of the application. There must be at least 1 of these
  • all databases should have dashboards
  • ideally also have at least cpu/mem utilization dashboards for webserver tier of the app
  • you can use plural from-grafana to convert a grafana dashboard found via google to our CRD
• Are scaling runbooks present
  • all databases must have scaling runbooks
  • you can use the charts in pluralsh/module-library to accelerate this
• do you need to add config overlays?
  • inputing secrets
  • configuring autoscaling
• If there’s a web-facing component to the app, we need to support OIDC authentication and setting up private networks if no authentication option is viable
• All major clouds must be supported
  • Azure
  • AWS
  • GCP

---

Checklist isn't very applicable because it's a simple doc add. Let me know if I missed anything 🍻

[michaeljguarino]

We can probably leave this part out of the airbyte docs (or explain its optional as well only if you want to ensure a 3 node spot pool)

[plural-bot]

🎉 This PR is included in version 1.2.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀