FP daemon startup fails if FP is jailed

[filippos47]

+ fpd start --eots-pk ee9da95e9fecbb2191943c56a109d1dc81787a77994ad9ef89278850a58e4876
2025-01-02T14:16:04.351563Z	info	Database closed
2025-01-02T14:16:04.351812Z	info	Stopping metrics server
2025-01-02T14:16:04.352180Z	info	Metrics server stopped gracefully
2025-01-02T14:16:04.352259Z	info	Metrics server stopped
2025-01-02T14:16:04.352426Z	info	Shutdown complete
service injective.evm.v1beta1.Msg does not have cosmos.msg.v1.service proto annotation
2025-01-02T14:16:04.676709Z	info	successfully connected to a remote EOTS manager	{"address": "localhost:12582"}
2025-01-02T14:16:04.700210Z	info	Starting FinalityProviderApp
2025-01-02T14:16:04.881456Z	debug	the finality-provider status is changed to JAILED	{"fp_btc_pk": "ee9da95e9fecbb2191943c56a109d1dc81787a77994ad9ef89278850a58e4876", "old_status": "JAILED"}
2025-01-02T14:16:04.881559Z	info	starting finality provider	{"pk": "ee9da95e9fecbb2191943c56a109d1dc81787a77994ad9ef89278850a58e4876"}
2025-01-02T14:16:04.881733Z	info	starting metrics update loop	{"interval seconds": 30}
Error: failed to start app: failed to start the finality-provider instance ee9da95e9fecbb2191943c56a109d1dc81787a77994ad9ef89278850a58e4876: failed to create finality provider instance ee9da95e9fecbb2191943c56a109d1dc81787a77994ad9ef89278850a58e4876: the finality provider instance cannot be initiated with status JAILED

Version: v0.14.2

[gitferry]

should be fixed by #260 which allows running of a jailed fp to submit randomness