Fix step-usage CodeLens anchor: connector method-name backfill never matched real wire data

[clrudolphi]

🤔 What's changed?

ConnectorDiscoveryService.BuildRegistry backfills the AST-precise method-identifier location for connector-discovered bindings (issue #484), meant to replace the connector's raw PDB sequence-point location — which lands on the first executable statement inside the method body, not the declaration line (the "N step usages" lens rendering below the method instead of above it).

That backfill compared sd.Method against Roslyn's bare MethodDeclarationSyntax.Identifier.Text, but DiscoveryResultTransformer.GetMethodReference (connector side) actually emits "{DeclaringTypeName}.{MethodName}({ParamTypeNames})" — e.g. "Steps.SetFirstNumber(Int32)" — never a bare name. The comparison could never match on real data, so every connector-discovered binding silently fell back to the imprecise PDB line. #484's own regression test passed only because its fixture used an artificially bare Method value that doesn't occur in production — masking the bug (that PR's "Live verification in VS Code" checklist item was also left unchecked).

• Added BindingImporter.ExtractBareMethodName to strip the wire-format reference down to the bare identifier before the name comparison, with pass-through for an already-bare name so existing callers/fixtures are unaffected.
• Added logging (verbose for the expected/benign "no local source" case, warning for a genuine parse/match failure) at each point the backfill can fail, so a stuck lens can be diagnosed from the server log going forward.
• Rewrote the demonstrating regression test to assert the fix instead of the bug (line/column now correct, no warning logged); added direct unit tests for ExtractBareMethodName.

⚡️ What's your motivation?

Investigating a live report that the step-usage CodeLens was still rendering below the binding method declaration led back to issue #484, which was believed fixed but never actually verified live. Digging into the fix revealed it was checking a name shape that real connector output never produces.

🏷️ What kind of change is this?

• 🐛 Bug fix (non-breaking change which fixes a defect)

🧩 Area(s) touched

• LSP server (src/LSP)

♻️ Anything particular you want feedback on?

The new tests prove the fix with realistic wire data, but I haven't done a live VS Code verification against a real built solution — worth doing before merge given #484's history of an untested fix shipping.

📋 Checklist:

• I've changed the behaviour of the code
  • I have added/updated tests to cover my changes.
• Users should know about my change
  • I have added an entry to the "[vNext]" section of the CHANGELOG, linking to this pull request & included my GitHub handle to the release contributors list.

🤖 Generated with Claude Code