Fix targetFramework detection incorrectly matching folder names containing "net" in deploy path

[Copilot]

The original TFM detection matched net anywhere in the deploy subpath string, causing false positives when project folder names contained net followed by digits/dots (e.g. Planet.net8.0, my_net8.0). This triggered a spurious mismatch warning and caused "Update VS Code config" to corrupt the folder name portion of azureFunctions.deploySubpath instead of updating the actual TFM segment. A lookbehind/lookahead approach still left two gaps: characters like _ or - before net satisfied the lookbehind, and .match() returning the first occurrence meant a project folder named like a TFM (e.g. net8.0/bin/Release/net6.0/publish) would be corrupted before the real TFM segment was reached.

Changes

• src/vsCodeConfig/verifyTargetFramework.ts: Replaced the generic targetFrameworkRegExp with a buildOutputPattern anchored to the known .NET build output path structure bin/(Debug|Release)/<TFM>:

// Before
const targetFrameworkRegExp: RegExp = /net(standard|coreapp)?[0-9.]+/i;

// After — anchors TFM detection to the known build output path segment
const buildOutputPattern: RegExp = /\bbin([/\\])(Debug|Release)\1(net(?:standard|coreapp)?[0-9.]+)/i;

The TFM is extracted from capture group 3 (always within bin/Debug/<TFM> or bin/Release/<TFM>), and the replacement function reconstructs only that segment while preserving the path separator and build type. For a path like net8.0/bin/Release/net6.0/publish, the pattern correctly identifies net6.0 as the TFM regardless of what precedes bin/.

[Copilot]

Pull request overview

This PR tightens .NET target framework detection in VS Code config verification to reduce false positives when deploy paths include folder names containing net.

Changes:

• Updates the target framework regex to avoid matching net... after letters, digits, or dots.
• Adds an inline comment explaining the folder-name false-positive case.

[nturinski]

@copilot apply changes based on the comments in this thread

[Copilot]

@copilot apply changes based on the comments in this thread

Applied in d105304. Replaced the lookbehind/lookahead approach with a pattern anchored to the known .NET build output path structure: /\bbin([/\\])(Debug|Release)\1(net(?:standard|coreapp)?[0-9.]+)/i.

This fixes both issues raised in the review:

1. Prefix characters like _/-: No longer a concern — the pattern only matches net... when it appears after bin/(Debug|Release)/, so my_net8.0/bin/Release/net6.0/publish correctly identifies net6.0 as the TFM.
2. First-match problem: Also fixed — the regex targets the TFM within the specific bin/Debug or bin/Release segment, so net8.0/bin/Release/net6.0/publish finds net6.0, not the project folder.

The replacement function reconstructs the matched segment (bin${sep}${buildType}${sep}${newTFM}) so only the TFM portion changes while the rest of the path is untouched.