Update sonarqube.md (#2214)

SonarQube has incremental analisys:

https://docs.sonarsource.com/sonarqube-server/latest/analyzing-source-code/incremental-analysis/introduction/

Author: evertramos

docs/faq/comparisons/sonarqube.md

@@ -20,7 +20,6 @@ Both Semgrep and SonarQube use static analysis to find bugs, but there are a few
 - Extending Semgrep with custom rules is simple since Semgrep rules look like the source code you’re writing. Writing custom rules with SonarQube is [<i class="fas fa-external-link fa-xs"></i> restricted to a handful of languages](https://docs.sonarqube.org/latest/extend/adding-coding-rules/) and requires familiarity with Java and abstract syntax trees (ASTs).
 - Semgrep supports user-defined autofixes; SonarQube does not.
 - Semgrep focuses on speed and ease-of-use, making analysis possible at up to 20K-100K loc/sec per rule. SonarQube authors [report approximately 0.4K loc/sec for rulesets in production](https://web.archive.org/web/20221109203440/https://community.sonarsource.com/t/performance-guide-for-large-project-analysis/148/2).
-- Semgrep supports scanning only changed files (differential analysis), SonarQube does not.
 - Both have publicly available rules
 - Semgrep has an online, hosted free plan for up to ten contributors to private repositories; both have a hosted paid plan.