refactor(REO): rename to RewardsEligibilityOracle, reduce initial requirements

[MoonBoi9001]

Summary

Renames the project from Service Quality Oracle (easy to confuse with Quality of Service Oracle) to Rewards Eligibility Oracle and reduces initial eligibility requirements for launch, to make for a smoother transition period.

Motivation

• Align naming with the oracle's actual purpose of determining rewards eligibility
• Reduce barrier to entry for initial launch by requiring only 1 subgraph instead of 10

Key Changes

Naming Updates

• Updated all references across:
  • Documentation (README, CHANGELOG, CLAUDE.md, ELIGIBILITY_CRITERIA.md)
  • Source code (blockchain_client.py, service_quality_oracle.py)
  • Tests (test_blockchain_client.py, test_configuration.py, test_service_quality_oracle.py)
  • Configuration (config.toml.example, k8s/configmap.yaml)
  • Contract ABI (contracts/contract.abi.json)

Eligibility Requirements

• Reduced MIN_SUBGRAPHS from 10 to 1 for initial launch
• Updated justification to focus on "syncing and serving subgraph data" rather than requiring multiple subgraphs
• Applied consistently across configuration, tests, and documentation

Additional Updates

• Fixed markdown linting in CLAUDE.md and STYLE_GUIDELINES.md

Impact

• Contract Interface: Updated ABI to match RewardsEligibilityOracle contract
• Configuration: All deployments will need to update config values
• Testing: All tests updated to reflect new requirements
• Documentation: Clear explanation of new eligibility criteria

Testing

All unit tests have been updated and pass with the new requirements.

[RembrandtK]

Name change looks good to me.