fix(ci): scope vscode publish workflow to extension tags

[eduardbar]

Summary

• remove ineffective release tag filter under release trigger
• gate the VS Code publish job to run only for vscode-v* tags or manual dispatch
• keep version verification active for both release and workflow_dispatch paths

Why

Core drift releases use vX.Y.Z tags and should not fail the VS Code extension workflow, which expects vscode-vX.Y.Z tags.

[github-actions]

drift trust

drift trust

• Trust Score: 78/100
• Merge Risk: MEDIUM
• Target: /home/runner/work/drift/drift

Diff signals

• Base ref: origin/master
• Diff status: NEUTRAL
• Score delta: +0
• Issues: +0 new / -0 resolved
• Trust adjustment: +0 penalty / -0 bonus (net +0)

Top reasons

• Maintenance hotspots: Maintenance risk is MEDIUM (35/100). (impact 9)
• Error-level issues: 2 error issue(s) increase merge volatility. (impact 8)
• Highest-risk file: /home/runner/work/drift/drift/src/guard.ts has hotspot risk 35/100. (impact 5)

Fix priorities

• feat(review): drift review command with PR comment output #1 large-file (error, x1, effort: high) - Split monolithic files by responsibility before merge.
• feat(score): repository quality score breakdown in scan/json #2 high-complexity (error, x1, effort: high) - Split branch-heavy functions before adding more logic.

drift review

drift review

ℹ️ No drift changes detected against base ref.

• Base ref: origin/master
• Score delta: +0
• New issues: 0
• Resolved issues: 0

File breakdown

• No file-level deltas detected