Fix muting of incorrect issues when bound to SonarCloud

[georgii-borovinskikh-sonarsource]

On version 7.5 and release candidate 7.6.0.82886 when a solution is bound to SC, the mark as resolved button incorrectly mutes a different issue with the same rule id in a different file.

The root cause is that when we match the issues, we expect them to be from the single file. However, because the request to SC was malformed, it actually returned issues from different files. The issue is that the same filter key is named differently on different servers: components for SQ and componentKeys for SC, and we only support the 1st one.