Should the templates be more specific with Azure Cosmos DB?

Azure Cosmos DB is a suite of database APIs: https://learn.microsoft.com/azure/cosmos-db

It includes:

- Azure Cosmos DB for NoSQL
- Azure Cosmos DB for MongoDB
- Azure Cosmos DB for MongoDB vCore
- Azure Cosmos DB for PostgreSQL
- Azure Cosmos DB for Apache Cassandra
- Azure Cosmos DB for Apache Gremlin
- Azure Cosmos DB for Table

At a minimum (short-term), I want to create a pull request to update the label from "Azure CosmosDB" to "Azure Cosmos DB" which is the official product name. I created a quick-fix PR in #460

Long-term, I would recommend adding some of the sub-service tags so we can be more specific about templates we're hosting on the site. I didn't feel comfortable generating a PR about this issue without further discussion. Most new samples are in the API for NoSQL, Table, PostgreSQL or MongoDB, so adding just those would go a long way towards splitting up the samples. But, I don't want to pollute the taxonomy. What does your team think?

Start by reviewing the issue and quick-fix PR #460, then inspect how Azure Cosmos DB labels and template categories are represented in the awesome-azd site. The short-term result is the official “Azure Cosmos DB” label; the long-term result requires a decided set of sub-service tags without polluting the taxonomy.

Written by the indexing model from the issue text.