Fix CodeLens positioned inside preceding code blocks

[adamint]

Description

Fix CodeLens being positioned inside preceding code blocks instead of on the resource declaration line.

Root cause: _findStatementStartLine() in both the C# and JS/TS AppHost parsers walked backwards from a resource match looking for ; or { as statement delimiters, but ignored }. When a code block like if (...) { ... } preceded a resource call, the algorithm walked past the } into the block and stopped at its {, placing the CodeLens inside the preceding block.

Fix: Add } as a statement delimiter in the backward walk so that closing braces correctly bound the start of the current statement.

Also fixes: tsconfig.json updated to include mocha types (resolves "Cannot find name 'test'" errors in VS Code) and skipLibCheck: true (resolves duplicate MCP type definition conflicts between @types/vscode and the proposed API file).

Validation: 26 new tests (13 C#, 13 JS/TS) covering: preceding if blocks, nested braces, blocks with semicolons, comments between blocks and resources (line comments, block comments, mixed comment styles), multi-line fluent chains, try/catch blocks, single-line blocks, empty blocks, for loops, multiple resources interspersed with blocks, and comments before fluent chains after blocks. All existing tests continue to pass.

Fixes #15618

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/microsoft/aspire/main/eng/scripts/get-aspire-cli-pr.sh | bash -s -- 15893

Or

• Run remotely in PowerShell:

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

[Copilot]

Pull request overview

Fixes incorrect CodeLens placement in the VS Code extension by improving how the AppHost parsers compute the start line of a resource statement when preceded by code blocks.

Changes:

• Update C# and JS/TS AppHost parsers to treat } as a statement delimiter when walking backwards to find statementStartLine.
• Add extensive unit tests for statementStartLine behavior around preceding blocks (C# + JS/TS).
• Update extension/tsconfig.json (mocha types, skipLibCheck) to address editor/test typing issues.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 5 comments.

File	Description
extension/tsconfig.json	Adds mocha/node types and enables skipLibCheck for TS build/editor experience.
extension/src/test/parsers.test.ts	Adds coverage for statementStartLine with preceding blocks and complex brace scenarios.
extension/src/editor/parsers/jsTsAppHostParser.ts	Includes } as a delimiter in statement-start detection for JS/TS AppHost parsing.
extension/src/editor/parsers/csharpAppHostParser.ts	Includes } as a delimiter in statement-start detection for C# AppHost parsing.

[JamesNK]

3 issues found: missing test coverage for callback-in-chain regression (1), skipLibCheck: true suppressing all .d.ts type-checking (1), minor edge case in } line-skip logic (1).

[github-actions]

Re-running the failed jobs in the CI workflow for this pull request because 2 jobs were identified as retry-safe transient failures in the CI run attempt.
GitHub was asked to rerun all failed jobs for that attempt, and the rerun is being tracked in the rerun attempt.
The job links below point to the failed attempt jobs that matched the retry-safe transient failure rules.

• Tests / Hosting-1 / Hosting-1 (windows-latest) - Job-level runner or infrastructure failure matched the transient allowlist.
• Tests / Hosting.DevTunnels / Hosting.DevTunnels (ubuntu-latest) - Failed step 'Build test project' will be retried because the job log shows a likely transient infrastructure network failure. Matched pattern: /Unable to load the service index for source https:\/\/(?:pkgs\.dev\.azure\.com\/dnceng|dnceng\.pkgs\.visualstudio\.com)\/public\/_packaging\//i.

[JamesNK]

There is some duplication. It would be good if parsing can be reused where possible. e.g. C#, TS and Java probably share some parsing logic because they're all C syntax languages.