Keep parsers up-to-date

[sonicfromnewyoke]

Problem

there is an often case when program updates their functionality (adds some fields to the structs or new instructions, etc) and Vixen Team can be informed about it only when someone will run into the issue and report it.

Proposed Solution

add cron-job (maybe github action) which will check IDLs once a day, downloads them and in case of diff with the previous version - generate parsers, or at least inform the team that something was changed here

Steps to Achieve

1. Create a script which will regenerate all the parsers from the stored IDLs. Can be taken in use as soon as will be written, because this is handy to actualize all the parsers just after the codama-renderers-vixen refactoring, improvements, new features, etc
2. create a script or maybe even a subprogram which will be responsible for finding the IDL and download it in the project. Some IDLs can be fetched from the official github repos, other from the chain, and subset of most "hidden" can be guessed with IDLGuesser
3. Check the diff of the stored IDL with the freshly downloaded. For the cases when IDL was guessed with IDLGuesser we have to store guessed idl in a couple with the human-readible one, for diff comparrison

cc @fernandodeluret

[fernandodeluret]

This is indeed something to take care of. What I can add to what you said is that the only 2 limitations I see towards a cronjob like approach are that a couple of our idls (only 1 or 2) are not publicly available (for example for one of them we build it out of the program source code). And the 2nd one is that we are still not quite at the 100% code generation (we are almost there, but there is still 1 or 2 manual tweaks we do after the generation), so until that this could be only for monitoring but not actual generation.

Also in this same regard we have recently added the deserialize_checked fn which does alert us in case an idl is unupdated