Inspect what rules indicate path not found and fix them if needed

[dsgouda]

Some paths returned by validation rules are not found in the document in which case we climb up the path.
While this is helpful, when working on composite documents the rule may end up pointing to a node that is common for all component files (eg. definitions)
We need to run the validator against the entire repo and inspect which rules run into this issue and evaluate if we can fix the paths returned by these rules so we can accurately point them using the vscode linter extension

Thanks @veronicagg for finding this issue.

A bunch of the rules could be cured of this issue by #2313

[dsgouda]

The first dependency, i.e., adding categorizations to each validation rule is done, we still need the rest spec repo to move to the configuration file formats here, post this reorg, we may be able to accurately investigate rules that fail to return proper paths.

[dsgouda]

Ran the AutoRest linter with our improvements related to validation categories over the reorg branch
Paths are not found consistently for the following rules and need to be investigated further

• TrackedResourceListByImmediateParent
• HttpsSupportedScheme
• OperationsAPIImplementation
• GuidUsage

[dsgouda]

• TrackedResourceListByImmediateParent/GuidUsage PR has been opened for the fix here: Better path reporting from trackedresourcelistbyimmediateparent #2373
• HttpsSupportedScheme paths not found are valid since the jsons did not have the schemes section
• OperationsAPIImplementation paths not found since the jsons did not have an operations API path