Commands are responsible for validating their parameters

[shuse2]

Expected behavior

All the params must be validated against the schema at some point.
Consider moving the schema validation into state machine where the params is decoded

Actual behavior

• CCMRegistrationPrams in https://github.com/LiskHQ/lisk-sdk/blob/89e7504ef5eb6183aefe576a93be3d6052e56038/framework/src/modules/interoperability/base_cc_commands/registration.ts#L51-L58 should be validated
• CCMSidechainTerminatedParams in https://github.com/LiskHQ/lisk-sdk/blob/89e7504ef5eb6183aefe576a93be3d6052e56038/framework/src/modules/interoperability/sidechain/cc_commands/sidechain_terminated.ts#L41-L48 should be validated
• TerminateSidechainForLivenessCommand does not validate params in https://github.com/LiskHQ/lisk-sdk/blob/89e7504ef5eb6183aefe576a93be3d6052e56038/framework/src/modules/interoperability/mainchain/commands/terminate_sidechain_for_liveness.ts#L30-L62

Steps to reproduce

N/A

Which version(s) does this affect? (Environment, OS, etc...)

6.0.0-alpha.2

[shuse2]

the reason why the property validation was done on each module was to ensure each module is responsible for writing the test for this.
If we move the validation to the state machine, the validation becomes responsibility of state machine and on the unit test, the param validation will not be tested on each module.
In the past, there was a bug introduced the bug because of this.

Additionally, for cross-chain command, currently the params is not decoded on submitCrossChainUpdate command. Therefore, if we introduce the validation, it will be required to decode twice unless we change the context