Replace ISolutionQueryOperations in hover with a dedicated service

[DustinCampbell]

When determining what projects a component or tag helper is available within, there is slightly different behavior in the Razor language server vs. co-hosting. In the language server, there is a special case to skip the misc-files project, but that case isn't bothered with in co-hosting. The special case is manifested via different implementations of ISolutionQueryOperations.GetProjectsContainingDocument(...) in the language server and co-hosting.

This change (which is largely mechanical) introduces a new service, IComponentAvailabilityService, that is used to determine what projects a component or tag helper is available within. The intention is that this service contains the behavior difference between the language server and co-hosting rather than relying on ISolutionQueryOperations, which will be going away with proper Razor solution snapshots.

[ryzngard]

Overall looks good. Some nits about location/namespacing that I don't think make sense after this change.

[davidwengier]

Is the plan that there will be some kind of ISolutionSnapshot available in cohosting and non, and when that happens the GetComponentAvailability method will get one of them as a parameter?

I can't imagine it working any other way (unless you're planning on introducing a "CurrentSolution" concept in cohosting, but that would be more surprising)

[DustinCampbell]

Is the plan that there will be some kind of ISolutionSnapshot available in cohosting and non, and when that happens the GetComponentAvailability method will get one of them as a parameter?

I can't imagine it working any other way (unless you're planning on introducing a "CurrentSolution" concept in cohosting, but that would be more surprising)

Yes, I was thinking that GetComponentAvailability would be passed an ISolutionSnapshot as the scope to search.

unless you're planning on introducing a "CurrentSolution" concept in cohosting, but that would be more surprising

I agree that would be surprising and I don't intend on doing that.

[davidwengier]

Yes, I was thinking that GetComponentAvailability would be passed an ISolutionSnapshot as the scope to search.

Awesome! I was going to suggest that could be done now by passing an ISolutionQueryOperations, and then later the param type could just be updated, but that would at least let the service be MEF exportable in cohosting, but I then figured since you'd already written the code it probably didn't matter much :)