Remove V3 engine check

[ag-ramachandran]

This pull request primarily refactors how the system checks if a table is a materialized view source and removes an unused method for determining if a table uses Engine V3. The logic for checking if a table is a materialized view source is simplified, and unnecessary code is eliminated.

Key changes include:

Refactoring and Code Simplification

• Removed the generateIsTableEngineV3 method from CslCommandsGenerator as it is no longer used.
• Simplified the logic in ExtendedKustoClient for checking if a table is a materialized view source by eliminating the Engine V3 check and directly returning the result.

[Copilot]

Pull Request Overview

This pull request removes an unused Engine V3 check functionality and simplifies the materialized view source detection logic. The changes eliminate unnecessary code complexity by removing the V3 engine validation step that was previously performed after determining if a table is a materialized view source.

Key changes include:

• Removed the generateIsTableEngineV3 method from CslCommandsGenerator
• Simplified the materialized view source check logic in ExtendedKustoClient to directly return the boolean result without additional Engine V3 validation
• Added a null safety check with proper Objects import

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
ExtendedKustoClient.scala	Simplified materialized view source detection by removing Engine V3 check and adding null safety
CslCommandsGenerator.scala	Removed unused generateIsTableEngineV3 method

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[github-actions]

Test Results

116 tests  ±0   116 ✅ ±0   17m 0s ⏱️ - 1m 7s
 24 suites ±0     0 💤 ±0 
 24 files   ±0     0 ❌ ±0 

Results for commit c89298a. ± Comparison against base commit ee8d1b1.

♻️ This comment has been updated with latest results.