fix: bump mcp-scan binary version to 0.4

[aarlaud]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

Bump mcp-scan binary in mcp-scan cli extension

Where should the reviewer start?

How should this be manually tested?

• make build
• snyk mcp-scan --experimental

What's the product update that needs to be communicated to CLI users?

Bump mcp-scan binary version

Risk assessment (Low | Medium | High)?

low