Route FROST authorization through registry

[mswilkison]

Summary

• route tBTC operator recognition, authorization, and sortition-pool checks through the FROST wallet registry when FROST authorization is configured
• use the FROST sortition pool for pool/reward/chaosnet status in FROST mode
• update generated FROST bindings and DKG result conversion types for the current contract ABI

Why

The local FROST testnet run showed that allowlisted operators could be provisioned on-chain, but keep-core still needed to use the FROST authorization source and sortition pool instead of the legacy ECDSA/staking path for operator lifecycle checks.

Validation

• go test ./pkg/chain/ethereum ./pkg/tbtc

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: cd3231a2-21a5-40ac-b7e9-9fa9539d020f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/frost-chain-authorization-routing

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}