docs: add status tables for all components

[andrzej-stencel]

Fixes #15654

How I got the details for the status tables for each component:

• Stability - this was the most tricky one; for some of the components, this information is not available. I put "unknown" for those and will kindly ask those components' maintainers to fill in the missing information.
  UPDATE: Thanks to all the code owners, all the missing stability level information is now filled in 🎉
• Supported pipeline types - I tried to get that from the rest of the description; hopefully got it right. Please comment if you think something needs to be changed.
• Distributions - This was the easiest, I looked at the manifests for core and contrib distributions. Hopefully I got this right.

[andrzej-stencel]

@pcwiese As the code owner for the Azure Monitor Exporter, can you specify the stability level of this component?

[andrzej-stencel]

@dashpole @billmeyer @gjanco As the code owners for the Mezmo Exporter, can you specify the stability level of this component?

[andrzej-stencel]

@Aneurysm9 @mxiamxia As the code owners for the AWS Proxy extension, can you specify the stability level of this component?

[andrzej-stencel]

@owais @dmitryax As the code owners for the Kubernetes Attributes Processor, can you specify the stability level of this component?

[andrzej-stencel]

@jrcamp As the code owner for the Receiver Creator component, can you specify the stability level of this component?

[andrzej-stencel]

@djaglowski @mcardy As the code owners for the Solace Receiver, can you specify the stability level of this component?

[djaglowski]

@djaglowski @mcardy As the code owners for the Solace Receiver, can you specify the stability level of this component?

I believe this one should be alpha.

[mcardy]

@djaglowski @mcardy As the code owners for the Solace Receiver, can you specify the stability level of this component?

We have one more unit of work we would like to have before this component should be stable (est. late November/early December timeframe). Either alpha or beta is sufficient for now, but after that work the component should be stable and ready for production use. We have done significant internal validation, so will be confident in the stability of the receiver by December.

[andrzej-stencel]

Wow, I didn't expect so good responsiveness, but it seems we have stability levels settled for all the components. Thank you to everyone involved! 👏 🎉 🏆

@bogdandrutu as the assignee, can you review this PR?

[dmitryax]

@astencel-sumo thanks for helping with this!