Improve searchability of Bicep snippets & resource names

If a user types in "containerapp" wouldn't it be awesome if we could show them related resources even if the name is something gnarly like "Websites.x.y@...". This should also work in the case that a user types in "resource blah ___" . We could allow them to type in "resource containerAppName "containerapp"" and they would be shown all of the resources with a similar tag. They would then be able to hit tab to receive the snippet for this resource.

I propose we start with our most commonly created resources and make them more searchable by adding in aliases for each resource.

What are the most confusing or nonsensical resource names?

The issue names no files, tests, or entry points; start by locating the Bicep snippet search and resource-name matching implementation. Clarify which commonly created resources need aliases and define done as matching names such as "containerapp" and supporting the proposed resource query and snippet completion behavior.

Written by the indexing model from the issue text.