Fix named string conversion diagnostics in bytescomparestring

[Copilot]

bytescomparestring recognized named string-type conversions but reported them as string(...), misrepresenting the flagged source expression.

• Diagnostic rendering
  • Preserve each conversion’s source type expression when building messages.
  • Render named types independently on both comparison sides.

type Password string

Password(a) == Password(b)
// diagnostic: Password(a) == Password(b) ...

• Regression coverage
  • Add golden coverage for Password(a) == Password(b).
  • Retain the existing bytes.Equal(a, b) suggested fix.

• Fixes bytescomparestring: diagnostic message hardcodes "string(...)" and misrepresents named-type conversions #53579

[Copilot]

Pull request overview

Corrects bytescomparestring diagnostics for named string conversions while preserving existing suggested fixes.

Changes:

• Render each conversion’s source type independently.
• Add named-string regression fixtures.
• Regenerate two unrelated workflow lockfiles, disabling strict mode.

Show a summary per file

File	Description
pkg/linters/bytescomparestring/bytescomparestring.go	Preserves conversion type expressions in diagnostics.
pkg/linters/bytescomparestring/testdata/src/bytescomparestring/bytescomparestring.go	Adds named-string regression coverage.
pkg/linters/bytescomparestring/testdata/src/bytescomparestring/bytescomparestring.go.golden	Verifies the unchanged suggested fix.
.github/workflows/mcp-inspector.lock.yml	Introduces unrelated non-strict workflow output.
.github/workflows/daily-team-evolution-insights.lock.yml	Introduces unrelated non-strict workflow output.

Review details

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

• Files reviewed: 5/5 changed files
• Comments generated: 2
• Review effort level: Balanced

[github-actions]

🎉 This pull request is included in a new release.

Release: v0.87.1