Fixed multichunk test (#1150)

## Description
<!-- Provide a brief summary of the changes made and the issue they aim
to address.-->
- The tests were showing flaky behaviour since the Link expiry check in
isChunkLinkInvalid() could trigger based on stub expiry times. This
caused extra refetch API calls intermittently (2 instead of 1)
- Test expected exactly chunkCount - 1 calls to verify
inline-first-chunk optimization
## Testing
<!-- Describe how the changes have been tested-->
Ran the test 10 times and it passed for all
## Additional Notes to the Reviewer
<!-- Share any additional context or insights that may help the reviewer
understand the changes better. This could include challenges faced,
limitations, or compromises made during the development process.
Also, mention any areas of the code that you would like the reviewer to
focus on specifically. -->
NO_CHANGELOG=true

Author: msrathore-db

src/test/java/com/databricks/jdbc/integration/fakeservice/tests/MultiChunkExecutionIntegrationTests.java

@@ -8,6 +8,7 @@
 
 import com.databricks.jdbc.api.impl.DatabricksResultSet;
 import com.databricks.jdbc.api.impl.DatabricksResultSetMetaData;
+import com.databricks.jdbc.common.DatabricksJdbcConstants;
 import com.databricks.jdbc.integration.fakeservice.AbstractFakeServiceIntegrationTests;
 import java.sql.Connection;
 import java.sql.ResultSet;
@@ -22,6 +23,9 @@ public class MultiChunkExecutionIntegrationTests extends AbstractFakeServiceInte
 
   @Test
   void testMultiChunkSelect() throws SQLException, InterruptedException {
+    // Ensure fake service property is set to skip link expiry checks in tests
+    System.setProperty(DatabricksJdbcConstants.IS_FAKE_SERVICE_TEST_PROP, "true");
+
     final String table = "samples.tpch.lineitem";
 
     // To save on the size of stub mappings, the test uses just enough rows to span multiple chunks.