Prepare BlazeMeter API Monitoring for official MCP Registry publication

[aabzm]

Summary

• Add the official MCP server ownership label to Dockerfile.
• Add versioned OCI registry metadata in server.json using the BlazeMeter API Monitoring name and direct token environment variable.
• Add a manual GitHub OIDC workflow that verifies project, registry, and OCI versions plus the published image label before validation and publication.
• Document the required image rebuild and manual publication command in README.md, with aligned product and image discovery metadata.

Validation

• Validated server.json against the official 2025-12-11 schema.
• Passed mcp-publisher v1.8.1 validation.
• Parsed the workflow YAML and executed its version and image guard scripts.
• Confirmed the current image is rejected because it lacks the required ownership label.
• Confirmed no credential values or OAuth variables are included.

[aabzm]

Publication remains blocked until ghcr.io/runscope/mcp-bzm-apitest:1.3.1 is rebuilt with io.modelcontextprotocol.server.name=io.github.runscope/mcp-bzm-apitest and republished.

[aabzm]

note that all of this, including the steps to get listed, were AI generated