Normalize handling of command telemetry from langserver and extension

Right now our command telemetry is handled mostly by the extension using the vscode-azuretools-ui package. Except for insert resource, which has a separate additional event for success and failure. If we want to have telemetry when used in other hosts like VS, we should make sure the langserver itself is able to handle basic command telemetry

The issue names no files or tests. Start by comparing the extension's existing command telemetry through vscode-azuretools-ui with the langserver path, including the separate insert-resource success and failure event. Define the basic telemetry contract needed by other hosts such as VS, and consider the work complete when both hosts can use consistent command telemetry.

Written by the indexing model from the issue text.