Stop running AINode (AIClusterIT) integration tests

AINode integration tests are temporarily disabled at the build and CI
level, without touching any test source code:

- integration-test/pom.xml: add the AIClusterIT category to
  excludedGroups in the AIClusterIT profile. includedGroups is kept so
  the profile stays scoped to the AINode tests only; excludedGroups
  takes precedence over includedGroups in maven-failsafe, so no AINode
  test is executed even when the profile is activated.
- .github/workflows/cluster-it-1c1d1a.yml: remove the "Cluster IT -
  1C1D1A / AINode" workflow. Its only job built AINode and ran the
  AIClusterIT integration tests, so it is no longer needed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: CRZbulabula

.github/workflows/cluster-it-1c1d1a.yml

@@ -544,7 +544,13 @@
                 <activeByDefault>false</activeByDefault>
             </activation>
             <properties>
-                <integrationTest.excludedGroups/>
+                <!-- Temporarily exclude all AINode (AIClusterIT) integration tests.
+                     includedGroups is intentionally kept as AIClusterIT so this profile stays
+                     scoped to the AINode tests only - leaving it empty would make failsafe run
+                     every IT in this module. The matching excludedGroups then skips them, and
+                     because excludedGroups takes precedence over includedGroups, no AINode test
+                     is executed even when this profile is activated. -->
+                <integrationTest.excludedGroups>org.apache.iotdb.itbase.category.AIClusterIT</integrationTest.excludedGroups>
                 <integrationTest.includedGroups>org.apache.iotdb.itbase.category.AIClusterIT</integrationTest.includedGroups>
                 <integrationTest.launchNodeInSameJVM>false</integrationTest.launchNodeInSameJVM>
                 <integrationTest.randomSelectWriteNode>false</integrationTest.randomSelectWriteNode>