fix: keep expected supplier endpoints aligned with overrides

[tsulhc]

Summary

The provider can repeatedly trigger ServiceMismatch remediation even when the supplier is correctly configured on-chain. The expected-service calculator ignored address-group endpointOverrides, while BuildSupplierServiceConfigHandler applied them when constructing the remediation stake transaction.

This change:

• Applies endpointOverrides when calculating expected supplier services.
• Adds shared RPC type normalization for numeric values, numeric strings, and enum names such as REST and JSON_RPC.
• Supports both legacy override keys such as "REST" and normalized numeric keys such as "4" in both validation and stake construction.
• Preserves the original endpoint value during {protocol} interpolation, avoiding unintended hostname changes and automatic restakes.
• Adds regression tests for both override-key formats and for the existing string-RPC interpolation behavior.

This keeps validation and remediation aligned without migrating existing endpoint hostnames or stored overrides.

Validation

GitHub Actions CI run #151 passed:

• Branch gate
• PR title validation
• Format check
• Lint
• Build
• Type check
• Tests
• No-console guard
• Docker builds for provider, provider-workflows, middleman, and middleman-workflows

[jorgecuesta]

Ey @tsulhc thanks for this contribution, can you change and point it to staging instead of main please.

[tsulhc]

Retargeted the PR to staging and addressed both review points. Override lookup is now backward-compatible with legacy enum-name keys and normalized numeric keys, while {protocol} interpolation continues to use the original endpoint value to avoid unintended hostname changes or restakes. Both review threads are resolved, and CI run #151 completed successfully, including all quality checks and four Docker builds.