[backport] Native query validation defaults to PostgreSQL when MariaDB and H2 driver in class path

[martinlippert]

Describe the bug
We are invalid VS Code SQL validation for Spring Data native queries after the latest update.

For projects using MariaDB native queries, the extension appears to fall back to PostgreSQL parsing/validation when it cannot find a MySQL connector on the classpath. This results in many false-positive validation errors for valid MariaDB SQL.

From looking at the code, I believe the relevant logic is here:
JdtDataQuerySemanticTokensProvider.java around line 120

spring-tools/headless-services/spring-boot-language-server/src/main/java/org/springframework/ide/vscode/boot/java/data/jpa/queries/JdtDataQuerySemanticTokensProvider.java

Line 120 in e4be66b

private SemanticTokensDataProvider getSqlSemanticTokensProvider(IJavaProject project) {

We are using the MariaDB java client as follow

runtimeOnly 'org.mariadb.jdbc:mariadb-java-client'

[BoykoAlex]

PR merged