Investigate how to notify team of upcoming chain updates

[sgerogia]

Adding a chain to Emeris means keeping up with (and planning for) future chain updates.

Before we can automate the task, we will need to understand the individual steps. At the very least we will need to be notified in advance of soft and hard forks.

These notifications will have to take place at a team-level. E.g. group Slack channel, team inbox

Maybe the existing Tracelistener etc infra could help by alerting w.r.t. to upcoming upgrade proposals on-chain. Or maybe a bot which tails Discord/Telegram channels etc

DoD

• Investigate appropriate notification method. E.g. automatic Github alerts, team inbox for chain teams to send notifications,...
• Set up the mechanism. E.g. Slackbot to dedicated channel, team inbox with team alias,...
• Make this part of the "Chain onboarding" process; set it up for every new chain

[RichardChester]

Initial ideas:

1. Using the plan endpoint provided by the upgrade module you could could create a dash board (most likely in Grafana) looking at current block hight and the block hight where the update will be required to provide a schedule/prioritisation for upgrades, could then also alert as we approach the upgrade height or even just send a "morning message" to a slack channel detailing the current update schedule.

1.1 This functionality (the upgrade height vs current height) could be included into the operator so that it becomes a seamless part of the chain onboarding process. This is potentially achievable by letting the operator log this information so that it can be aggregated by Loki.

2. Include cosmovisor (https://github.com/cosmos/cosmos-sdk/tree/master/cosmovisor) into the docker images running the nodes. The documentation for cosmovisor recommends using its auto update feature for full non-validator nodes which is our use case.

[akc2267]

moving to close as this has been investigated and I'd like to move onto more prioritized issues