Merge DevRev MCP Connector

This PR adds the DevRev MCP server to the Cursor collection.

The DevRev MCP server uses the Streamable HTTP transport protocol.
Based on other MCP server entries, I have specified “transport”: [“http”].
Please let me know if this is the correct approach.

The DevRev MCP server supports OAuth. Do we need to provide a client ID
as part of the configuration? In which cases is the domain field required?

Relevant issue: #109

Are there any additional details we would have to submit to get DevRev enabled on cursor? A lot of our customers user Cursor and we want to give them the support of using our MCP.

Thank you.