Resource type completion sort order should account for API version suffixes

[majastrz]

The resource type completions are currently sorted ascending by the fully qualified resource type and then descending by the API version. The API version component is sorted lexicographically, which can give priority to wrong suffixes.

We should implement a comparer that sorts resource types more accurately.

[miqm]

I think that we have way too much completions provided and it's not very useful now. longer types (often child resources) are being cut in the middle, resulting that you still need to know the type you're looking for.

I'dlike to ssuggest changing completions from one list of type&api to segmented approach like in C# namespaces - you would get each type fqdn frament separately.

less robust approach is to separate completions of type and api - first choose type, then api version.

or perhaps a mix of those: when you have some part of the type alredy entered, in completion window just show remaining type part, not entire type (will avoid cutting long types)

[miqm]

I just realised that I wrote similar idea in #1060.

one thing is api version sorting and second is type selection, so I'll move my idea there and leave this for the api sorting.