Summary
This update addresses a bug where getGeneratedKeys() fails for INSERT statements that begin with SQL comments (e.g., /* ... */ INSERT ...). The method previously relied on a naive string check that only matched queries starting directly with "INSERT", causing errors or missing generated keys. This PR revises the logic to correctly identify and handle INSERT statements even when preceded by comments.

Background (Issue #2729)
Issue: When executing an INSERT statement that begins with a comment and requesting generated keys, the call to getGeneratedKeys() fails with an unrelated error:

com.microsoft.sqlserver.jdbc.SQLServerException: The statement must be executed before any results can be obtained.
This happens because the driver does not send the identity retrieval command when the SQL string doesn’t start with "INSERT" 
[GitHub](https://github.com/microsoft/mssql-jdbc/issues/2729)

.
What Changed
Updated the logic in SQLServerStatement (within the getGenerateKeys() handling) to use the internal isInsert() utility method, which:

• Trims leading whitespace.
• Skips initial SQL comments.
• Recursively checks if the actual statement begins with "INSERT"
  This change ensures that identity retrieval is correctly triggered for valid INSERT statements even if comments precede them.

Impact
Fixes getGeneratedKeys() issue when SQL statements have leading comments.
Resolves the user-reported bug in #2729, aligning behavior with user expectations.

Testing
Manually tested locally and added a test case with an INSERT statement that starts with a comment:

stmt.executeUpdate("/* comment */ INSERT INTO ...", Statement.RETURN_GENERATED_KEYS);
ResultSet rs = stmt.getGeneratedKeys();

Now, the generated keys are returned as intended

Closes: Issue #2729