Fail hard when C# and VB.NET plugins are missing on the server

[pavel-mikula-sonarsource]

Plugins are now bundled with their respective SQ version. And users are not supposed to uninstall or change them.

For S4NET v6, we should fail hard in case that happens to prevent unexpected analysis behavior caused by broken or out-of-sync clusters. We had an issue on Peach farm where some SQ nodes had old plugins and S4NET was not able to fetch them. This resulted in successful analysis with no issues to be reported silently.

08:09:05.548  Updating build integration targets...
08:09:06.254  Fetching analysis configuration settings...
08:09:07.241  Provisioning analyzer assemblies for cs...
08:09:07.249  Installing required Roslyn analyzers...
08:09:07.868  08:09:07.868  WARNING: Plugin resource not found: vbnet, version 8.53.0.62527. Resource: SonarAnalyzer-8.53.0.62527.zip. The rules for this plugin will not be executed.
08:09:08.151  Provisioning analyzer assemblies for vbnet...
08:09:08.151  Installing required Roslyn analyzers...
08:09:08.183  08:09:08.183  WARNING: Plugin resource not found: vbnet, version 8.53.0.62527. Resource: SonarAnalyzer-8.53.0.62527.zip. The rules for this plugin will not be executed.
08:09:08.215  Pre-processing succeeded.

[andrei-epure-sonarsource]

ToDo: we should talk with Services / Sales Engineering whether this is a customer-facing scenario (multiple clusters getting out of sync).

Test scenario: ensure it works with non dotnet MSBuild executions.

cc @tom-howlett-sonarsource

[pavel-mikula-sonarsource]

A question was sent to services today

[pavel-mikula-sonarsource]

Services team is not aware of such a problem on user side.