Monitoring Configurations improvements

[radu-stefan-dt]

Summary
Monitoring configurations used with the Copilot should be validated/enchanced more.

Current behavior
Currently these files & configuration object offer very little help. There are only some limited suggestions for local scopes (Host, Host Group). In addition, the schemas used for generating the configuration objects are based on Dynatrace schema, not pure jsonSchema, meaning that VSCode will struggle to offer native validation and suggestions.

Proposed improvements
There are a series of improvements which can be made:

1. Schemas used in generating configs should be converted (or augmented) with standard jsonSchema attributes so that VSCode can natively highlight discrepancies and offer suggestions
2. Schemas should use defaultSnippets so writing them becomes faster with entire objects populated by VSCode
3. Schemas should offer suggestions for featureSets and vars from the extension manifest.
4. Scope completion suggestions should be extended to cover ActiveGates and Management Zones if the API Token scope allows it
5. Custom diagnostics should be employed when jsonSchema doesn't offer enough logic or a clearer message is needed than what's offered by jsonSchema (e.g. "Object matches a schema that is not allowed" - doesn't help fix the problem)

• Fix actions may be something to explore here