Improve lisk-codec protocol specs to be more deterministic

[nazarhussain]

Description

The protocol specs of any component in the system must be deterministic, means input and output must defined explicitly for every case. And there must not be any modifications/mutations to output/input runtime to pass the tests.

Currently we have protocol specs for lisk-codec encoding behaviour, but we don't have it for decoding behaviour. And as per our implementation of lisk-codec and by specification of the LIP the encoding and decoding may not turn out be same as always. e.g. Its a viable chance that in example below data and reverseData may not match strictly because of the default values for properties which are not defined in the data object.

const data = {a: 1, b: 2}
const binary = codec.encode(schema, data);
const reverseData = codec.decode(schema, binary);

To cover this part we had a lot of custom manipulation of protocol specs in test suites, which does not fulfil the purpose of having protocol specs. e.g. few of reference mentioned below. We need to improve these and protocol specs must define the decoding specs and we should avoid runtime mutation of specs input/output in our tests

lisk-sdk/elements/lisk-codec/test/decode.spec.ts

Lines 67 to 71 in 2db69cd

	expect(result).toEqual({
	...testCase.input.object,
	number: BigInt(testCase.input.object.number),
	});
	});

lisk-sdk/elements/lisk-codec/test/decode.spec.ts

Lines 113 to 117 in 2db69cd

	expect(result).toEqual({
	...testCase.input.object,
	balance: BigInt(testCase.input.object.balance),
	address: Buffer.from(testCase.input.object.address?.data as number[]),
	});

lisk-sdk/elements/lisk-codec/test/decode.spec.ts

Lines 161 to 167 in 2db69cd

	expect(result).toEqual({
	...testCase.input.object,
	myArray: testCase.input.object.myArray?.map(l => ({
	...l,
	amount: BigInt(l.amount),
	})),
	});

Motivation

The protocol specs for Lisk-Codec must deterministic and cover both encoding and decoding behaviours.

Additional Information