Docs improvements

[matthchr]

• Add to diagnosing issues, section about diagnosing issues with free tier API server. "Error from server (InternalError): error when creating "/tmp/asd": Internal error occurred: failed calling webhook "
• Add documentation about how to compose on top of ASO (Common architectures?)
• Details about how "owner" works + examples. When should you use Kubernetes ownership, versus raw ARM IDs?
• Adoption, how does it work?
• Security best practices - warning about RoleAssignment
• Security best practices - discussion of how to structure namespace/secret management. Recommendation to avoid global secret.
• Security best practices - How to safely scope a namespace to manage only a single RG.
• Experimental release best practices
• How to run your local copy of ASO in your AKS cluster (This is sorta a developers guide thing rather than an end user thing)
• How to add a handcrafted resource (i.e. how to deal with POST)
• https://azure.github.io/azure-service-operator/guide/installing-from-yaml/ doesn't mention crdPattern
• Discuss "what we are not" - at least with respect to templating. We are not trying to generically solve templating - use Kustomize or Helm or insert your favorite Kuberentes templating engine here. Helping to answer the issue here: Add support for reading name or armId in all KnownResourceReference fields from Secrets and ConfigMaps #3827

[matthchr]

Thinking it might be nice to do a doc hack for 2-3 days and get all of us working on documentation improvements from either the above list or other issues.

[matthchr]

Not doing this one here:

• https://azure.github.io/azure-service-operator/guide/installing-from-yaml/ doesn't mention crdPattern

Instead will track it via #3719

[matthchr]

Closing this, will make a new issue for the one remaining item: " How to add a handcrafted resource (i.e. how to deal with POST)"