Improve support for .asmdef references, including GUID references

[citizenmatt]

This PR builds on #2174 to improve support for .asmdef files. It's currently targeting that branch, but will automatically switch to net213 when merged. Some minor conflicts will need to be addressed, since #2174 has moved on a little bit since this branch started.

• Re-enable highlighting of resolve errors for references inside a .asmdef file. Process files from all external packages #2174 now indexes all .asmdef files from all packages, so we can resolve all references, even into builtin packages/modules. Fixes Custom PSI module for external assembly definition files #702
• Adds support for GUID based references, which are preferable because they are based on asset GUID, rather than a name that could change. GUID references are now resolved, and work with CTRL+click and Find Usages, as well as context highlighting. These references are not affected by a rename refactoring of the assembly definition name.
• GUID based references show the resolved name of the referenced assembly definition in a tooltip and an inlay hint. The hint can be configured from the alt+enter menu, and also from a new Unity inlay hints options page. Resolves RIDER-58568
• Add a hint to prefer GUID based references to user-editable .asmdef files that are using name based references. The hint severity is configurable.
• Add a scoped Quick Fix to convert name to GUID based reference, just once, or in file/folder/project/solution. Add a similar scoped context action to convert GUID references to named references.
• Update inspection highlights to only highlight the unquoted part of a name, rather than the full quoted range
• Fix a bug when removing an invalid item from the references array that would leave a dangling comma (e.g. when referencing self)
• Added as many tests as possible

[krasnotsvetov]

Could you check that JetBrains.ReSharper.Plugins.Unity.JsonNew.Feature.Services.Daemon.JsonNewLanguageSpecificDaemonBehavior is applicable for asmdef files? That behaviour suppresses swea for asmdef. We are not calculating any dependencies for asmdef files so reanalyze after changes is not working for asmdef files

[citizenmatt]

Aha, yes, it applies. And we don't get any errors in SWEA if there's an error in a .asmdef file. Should we change RunInSolutionAnalysis to return true?

[krasnotsvetov]

No, because asmdef is not supporting swea right now: if you create asmdef file with unknown guid, that error will be added to swea. After that, close that asmdef file and fix error by creating required asmdef, error will not disappear from solution-wide analysis, swea will not reanalyze first file, because we don't provide any info why the file should be reanalyzed

[citizenmatt]

We've got a file watcher on all external files, and push the PSI changes through the change builder, so we're updating caches (like we're doing with assets and scenes, etc.). Is that enough for SWEA, or does it need more?