Bump VS Code extension version from 1.0.3 to 1.0.4

[Adam Ratzman (adamint)]

Description

Bumps the VS Code extension package.json version from 1.0.3 to 1.0.4.

Fixes # (issue)

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire.dev issue:
      • New issue
  • No

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 14860

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/dotnet/aspire/main/eng/scripts/get-aspire-cli-pr.ps1) } 14860"

[Copilot]

Pull request overview

This PR bumps the Aspire VS Code extension’s published version in extension/package.json from 1.0.3 to 1.0.4, which is used by the extension packaging pipeline to produce versioned VSIX artifacts.

Changes:

• Update VS Code extension package.json version to 1.0.4.

[Copilot]

The extension version was bumped in package.json, but extension/package-lock.json still has the root package version set to 1.0.3 (top-level "version" and packages[""].version). This leaves the repo in an inconsistent state for anyone using npm-based workflows; please update or regenerate the lockfile (or remove it if it's intentionally unused).

Suggested change

	"version": "1.0.4",
	"version": "1.0.3",

[Copilot]

PR description includes a placeholder “Fixes # (issue)”. Please either link the actual issue/PR being fixed or remove this line so release notes/auto-linking don’t end up with an invalid reference.