[Feature]: DevTool "supported messages" mechanism

[cpaulve-1A]

Context

When using the Otter DevTool there is nothing preventing the user to run it on a version not compatible with the latest features or messages. For instance, whenever we want to evolve messages or create a new one, it won't work with the previous versions even if it could be still be done in a less efficient way.
For example, the initial updateTranslation message can only contain a key at a time. Since then, the state panel allows to restore a whole override set with possibly a bunch of translations.
If we want to be compatible with the supported versions, we cannot modify the message api to optimize the flow.
We also cannot warn a user if some features cannot be used in their full capabilities.

Proposal

Create a mechanism where the application can submit the list of messages it supports so that the DevTool can either adjust its behaviour or warn the user that some features may not work and encourage them to migrate to the latest versions