Fix PreparedStatement getGeneratedKeys() returning "statement must be executed" error when triggers are present

Problem:

• PreparedStatement.getGeneratedKeys() was failing with "The statement must be executed before any results can be obtained" when INSERT statements had triggers

Root Cause:

• PR #2737 correctly made SQLServerPreparedStatement.hasUpdateCountTDSTokenForInsertCmd() return false to fix update count issues for multi-statement queries
• However, this change did not account for the generated keys use case where bRequestedGeneratedKeys is true
• When hasUpdateCountTDSTokenForInsertCmd() returns false for PreparedStatement, it affects the TDS token processing in such a way that the generated keys ResultSet is not properly consumed or made available
• When triggers fire and generated keys are requested, additional TDS tokens must be processed to locate the ResultSet containing the generated keys

Solution:

• Modified hasUpdateCountTDSTokenForInsertCmd() to return true when generated keys are requested (bRequestedGeneratedKeys = true)
• This maintains the correct update count behavior for multi-statement queries while preserving generated keys functionality
• The conditional approach ensures both scenarios work correctly without breaking existing functionality

Testing:

• Validates both update count accuracy and generated keys retrieval work correctly with triggers
• Ensures multi-statement PreparedStatement queries still return correct update counts
• Covers the specific scenario reported in issue Generated keys no longer returned if there is a trigger on insert #2740

Fixes #2740