Bump @microsoft/vscode-azext-utils to 4.1.0

[Copilot]

Updates the extension to consume @microsoft/vscode-azext-utils ^4.1.0 and regenerates the lockfile so the bundle resolves to that version. Related azext packages were reviewed and did not require version changes to avoid pulling an older utils release.

• Dependency update

  • Bumped @microsoft/vscode-azext-utils in package.json from ^4.0.7 to ^4.1.0.

• Lockfile refresh

  • Re-ran npm install to update package-lock.json and capture the new transitive dependency graph from utils 4.1.0.

• Bundle resolution

  • Kept @microsoft/vscode-azext-azureutils and @microsoft/vscode-azext-github at their current versions because their declared ranges already admit utils 4.1.0, allowing npm to dedupe to a single installed utils version.

{
  "@microsoft/vscode-azext-azureutils": "^4.0.1",
  "@microsoft/vscode-azext-github": "^2.0.1",
  "@microsoft/vscode-azext-utils": "^4.1.0"
}

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.