Unify the baking command arguments under the agnostic baker

Currently, if someone decides to add a new command line argument for the baker of an active protocol (say Y), they are not warned in any way that this new option must be backported to the other active protocols (say X). Consequently, if Y contains a mandatory option --do-this, and the code for baker X does not have this option, the users will upgrade their octez binaries (which includes the agnostic baker), then they will run the baker command the same way (it will run protocol X) and it will not complain, because the mandatory option for Y is not yet required. But, when the migration time comes, the baker will have an error, because the Y will require the mandatory option. What we need is a way to prevent the developers from being able to create a new option, without backporting it to all other active protocols, such that the agnostic baker migrates gracefully (meaning when the octez version is upgraded, the run for protocol X will actually be able to use the new option that say is needed only from Y and for X is a no-op).

An investigation needs to be conducted if a similar issue is already solved in the agnostic rollup node.