Description:

Currently, the OP client controller depends on the off-chain Finality Gadget to function, specifically for calling QueryActivatedHeight which internally uses QueryBtcStakingActivatedTimestamp:
https://github.com/babylonlabs-io/finality-provider/blob/main/clientcontroller/opstackl2/consumer.go#L449-L472

🔴 Problem:
This introduces an unnecessary dependency, as every BSN may implement or choose not to implement their own version of the Finality Gadget. Finality Providers (FPs) should not rely on it or have any references to it.

⚠️ Some external teams have worked around this by manually setting the activated height via a flag, but this is not ideal.

✅ Action:
We need to define a better way for the OP client controller to handle activation height without relying on the Finality Gadget.