[microsoft.azd.extensions] Fix azd x watch glob matching on Windows and enable CI tests

[JeffreyCA]

Summary

Follow-up to #8273. Two related changes:

1. Fix glob matching on Windows. The hardcoded ignore fast-path in shouldIgnoreWatchEvent was using doublestar.PathMatch, which splits patterns on the OS path separator. On Windows that separator is \, so multi-segment patterns like bin/**/* could never match the forward-slashed relPath produced by filepath.ToSlash. Switched to doublestar.Match, which always splits on / and matches the convention already in use for relPath and the hardcoded patterns. This is the library's documented recommendation when both inputs are forward-slashed.

2. Enable unit tests in CI for microsoft.azd.extensions. The pipeline had SkipTests: true and the extension was missing ci-test.ps1. Without these, the existing TestShouldIgnoreWatchEvent* tests (and any future tests) never run in CI, so Windows-only regressions like (1) can slip through. Mirrors the setup used by other extensions (e.g. azure.ai.agents).

User impact of the matching bug

In practice on Windows the broken matcher was largely dormant:

• watchRecursive skips ignored folders by directory name at any depth via filepath.SkipDir, so bin/, obj/, build/, node_modules/, and .git/ are never added to the watcher.
• fsnotify on Windows is non-recursive, so events for files inside non-added directories never surface to shouldIgnoreWatchEvent.
• Single-segment patterns (bin, *.spec, package-lock.json, ...) still matched correctly even with the OS-separator bug.

The fix removes a latent footgun and makes the existing TestShouldIgnoreWatchEvent* unit tests pass on Windows. Linux and macOS were unaffected.

Verification

cd cli/azd/extensions/microsoft.azd.extensions
go test ./internal/cmd/...
# ok  github.com/azure/azure-dev/cli/azd/extensions/microsoft.azd.extensions/internal/cmd

pwsh ./ci-test.ps1
# All tests passed!

[Copilot]

Pull request overview

Fixes Windows-specific glob matching in azd x watch by aligning doublestar glob evaluation with the forward-sash (/) normalization already used for watcher event relative paths.

Changes:

• Replace doublestar.PathMatch with doublestar.Match in shouldIgnoreWatchEvent to correctly match multi-segment patterns like bin/**/* on Windows.
• Add an inline comment explaining why Match is required given relativeWatchPath returns forward-slashed paths.

[hemarina]

LGTM — no blocking or non-blocking issues found.

The Windows glob matching fix uses the correct doublestar API for forward-slashed relative paths, and the CI test enablement follows the existing extension pipeline pattern.

[JeffreyCA]

/check-enforcer override