bug: expired ibc-client on restart

## Overview
If there is a restart of the pods for whatever reason, it seems that the ibc client get expired fairly quickly.

> Note: IBC client expiry is not limited to restarts of pods. So this needs to be solved more genrally as well.

## Proposal
We should add a way to revie an IBC-client.
Initial thought is to have an `/ibc/client-prop` endpoint (we can have a better name), on the exposer itself. This can provide admin functions to submit a gov prop, pass it: for the ibc client

We can also just create an endpoint to be more specific to revive a

## Alternatives
* Work with timeouts, to have a more reasonable setting. Expose this to the config, so this is user defined and specific
* Have traffic emulators running, that will keep performing txns on the chains to emulate ibc transations as well. This will make expriy of clients more rare.

Start by reviewing the proposed /ibc/client-prop endpoint on the exposer and the stated alternatives for IBC-client expiry. The issue does not name files or tests; done should address expiry after pod restarts and the broader expiry case, with a defined administrative recovery path.

Written by the indexing model from the issue text.