chore: update @microsoft/vscode-azext-utils to ^4.1.0

[Copilot]

Bumps @microsoft/vscode-azext-utils to ^4.1.0 (released) and regenerates the lockfile so only 4.1.0 ends up in the bundle.

Changes

• package.json: @microsoft/vscode-azext-utils: ^4.0.7 → ^4.1.0
• package-lock.json: regenerated via npm install

No other packages required updating — @microsoft/vscode-azext-azureutils (^4.1.0) already resolves a compatible version, and the other potentially affected packages (azureappservice, azureappsettings, github) are not present in this repo.

Original prompt

Version 4.1.0 of @microsoft/vscode-azext-utils has been released.

1. Update @microsoft/vscode-azext-utils to ^4.1.0 in package.json.
2. If @microsoft/vscode-azext-azureutils, @microsoft/vscode-azext-azureappservice, @microsoft/vscode-azext-azureappsettings, or @microsoft/vscode-azext-github are present and require a version of @microsoft/vscode-azext-utils older than 4.1.0, update those packages to their latest versions as well so only utils 4.1.0 ends up in the bundle.
3. Run npm install to regenerate the lockfile.
4. Ensure existing tests still pass.

[Copilot]

Pull request overview

Routine dependency bump of @microsoft/vscode-azext-utils to ^4.1.0, with the lockfile regenerated so only 4.1.0 is installed.

Changes:

• Bump @microsoft/vscode-azext-utils from ^4.0.7 to ^4.1.0 in package.json.
• Regenerate package-lock.json to resolve utils at 4.1.0 and pick up the transitive @vscode/extension-telemetry ^1.5.2 bump.

Reviewed changes

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

File	Description
package.json	Updates the declared version range for @microsoft/vscode-azext-utils to ^4.1.0.
package-lock.json	Regenerated lockfile entries reflecting utils 4.1.0 and updated telemetry dep range.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.