Configuring a SonarQube connection / updating the binding fails when more than 10K projects+modules are defined in SonarQube.
When the user defines a SonarQube connection, SonarLint calls api/components/search to get the whole list of projects that the user has access to. This is currently required for the user to easily search and choose a project to bind with.
But, SonarQube doesn't return more than 10K projects/modules and throw a HTTP 400 - bad request when SonarLint ask for more. This is the behavior for different APIs that involve Elasticsearch like also api/issues/search.
SonarLint should not try to query more than 10K projects/modules. And, when the project can't be found within this set of projects, the user will be able to manually enter the exact key of the project/module.