General documentation for Multi-Team Airflow

[o-nikolas]

Rendered docs:

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[Srabasti]

Looks like typo "perimiter -> "perimeter" is causing spell check to fail.

[o-nikolas]

Looks like typo "perimiter -> "perimeter" is causing spell check to fail.

Thanks for the review @Srabasti! 😃 I will fix that.

Note: Please don't put a Request for Change on a PR unless the change is absolutely critical and there is no way it should be merged. Otherwise it makes it difficult to merge afterwards until the request is cleared (or it's cleared manually).
In this case the failing build will be enough to block merging until it is fixed 🙂

[ferruzzi]

LGTM