fix: Fix to manual scaling setting handling in 005ccbbd-aeab-46ef-80bd-9bd4479412ec

[Takeshi Katano (tksh164)]

Overview/Summary

Fixes to the manual scaling setting handling in 005ccbbd-aeab-46ef-80bd-9bd4479412ec.

Related Issues/Work Items

• 🪲 Bug Report - Does not catch AKS cluster with Manual scale node pool correctly #749

Breaking Changes

• None

As part of this pull request I have

• Read the Contribution Guide and ensured this PR is compliant with the guide
• Checked for duplicate Pull Requests
• Associated it with relevant GitHub Issues or ADO Work Items (Internal Only)
• Ensured my code/branch is up-to-date with the latest changes in the main branch
• Ensured PR tests are passing
• Performed testing and provided evidence (e.g. screenshot of output) for any changes associated to ARG queries
• Updated relevant and associated documentation (e.g. Contribution Guide, Docs etc.)

Screenshots

[Copilot]

Pull Request Overview

This PR refines the AKS node pool query to correctly handle manual vs. auto-scaling scenarios and makes the type filter case-insensitive.

• Changes the resource type match to use case-insensitive operator (=~).
• Splits taint and scaling filters, adding separate logic for enableAutoScaling true/false.
• Updates projection to include the enableAutoScaling flag and conditionally show minCount or count.

Comments suppressed due to low confidence (1)

azure-resources/ContainerService/managedClusters/kql/005ccbbd-aeab-46ef-80bd-9bd4479412ec.kql:10

• Add or update unit/integration tests to cover both enableAutoScaling = true and enableAutoScaling = false paths to ensure the query filters correctly in each scenario.

| where (agentPoolProfile.enableAutoScaling == true and agentPoolProfile["minCount"] < 2) or (agentPoolProfile.enableAutoScaling == false and agentPoolProfile["count"] < 2)