We should get rid of the "resource-{,without-}defaults" and "resource-child-{,without-}defaults" snippets

[StephenWeatherford]

We should check telemetry, but I'm guessing these are rarely used. I think we should at least get rid of the "without-defaults" versions.

1. Now that we have lots of resource snippets, I think these just clutter up the namespace and cause confusion:
2. They're not really useful (esp the without-defaults ones), you can just type "resource" and use intellisense
3. They lead you away from the better intellisense experience of having properties automatically filled out from the actual resource type once you've selected it:

[StephenWeatherford]

TODO: Check telemetry for usage and get back to triage with recommendations.

[anthony-c-martin]

+1, I think the 'required-properties' snippet is way more valuable as it's type-aware; I'd much rather point people towards that.

[majastrz]

Agree. If telemetry shows no meaningful usage, we should remove.

[ucheNkadiCode]

@StephenWeatherford after findings in telemetry usage, I support removing both. #sign-off

[StephenWeatherford]

All four?

[alex-frankel]

Plan is to get rid of the above 4 and replace with single "resource" snippet that fills in the following:

resource {name} '{provider/type}@{api-version}' = 

With tab stops in the spots with {...}

[StephenWeatherford]

Work with Mikolaj and Ben.

[StephenWeatherford]

P1 for next milestone