feat: Deploy TestReputationRegistry to Celo Mainnet and update contract constants

[DianaRicee]

PR Description

Summary

This PR introduces the Celo Mainnet deployment of the TestReputationRegistry contract, along with minor adjustments to contract parameters and constructor initialization.

Key Changes

📄 Contract: TestReputationRegistry.sol

• Adjusted Reputation Constants
  • Changed MAX_REPUTATION from 1100 → 1000 for a more standardized scoring scale.
  • Retained MIN_REPUTATION = 0 and INITIAL_REPUTATION = 500 for balanced defaults.
• Updated Constructor
  • Added a string info = "Test 3" for testing/deployment traceability.
  • Keeps contract lightweight while enabling version/debug tracking.

📂 Deployment: broadcast/DeployTestReputationRegistry.s.sol/42220/run-latest.json

• Added Celo Mainnet deployment metadata including:
  • Contract Address: 0x1ee41a6f09b0458bac30f0a61fcca02c94b750e4
  • Deployment Transaction Hash: 0x6f86cb902bad751500a01a86e5c8f43d8e3f5f972ababfdb69c98533c1f6282b
  • RegisterSelf Transaction Hash: 0x1edc144e1dbd4080960ec329020995327f9daad57af0bdcfa6c2b0e896942b28
  • Verified successful contract creation and event emission (UserRegistered).

Motivation

• Standardization: Setting MAX_REPUTATION to 1000 ensures a clear upper bound that’s easy to reason about.
• Deployment Traceability: Including "Test 3" in the constructor makes it easier to distinguish deployments across environments.
• Network Expansion: Deploying to Celo Mainnet provides a production-ready registry to support ecosystem use cases.

Next Steps

• Add Celo Alfajores testnet deployment for staging validation.
• Consider introducing a versioned constructor parameter rather than hardcoded test strings.
• Expand unit + integration tests for Celo deployments to confirm event emissions and gas usage.