refactor done seprated constants from config

[LijuJoseJJ]

this PR fixes https://.com/EYBlockchain/nightfall_3_private/issues/158

[Westlad]

I think we need to be careful about the definition of a config item and a constant. A constant will never depend on the details of our deployment. An example is ZERO: 0x000..... A config item is something that is deployment dependent, for example the name of a Mongo collection or the height of a Merkle tree. There are only a few grey areas, such as the definition of calldata types. These could arguably be either but are best categorised as constants because they will actually never be dependent on the details of a deployment.

[LijuJoseJJ]

I think we need to be careful about the definition of a config item and a constant. A constant will never depend on the details of our deployment. An example is ZERO: 0x000..... A config item is something that is deployment dependent, for example the name of a Mongo collection or the height of a Merkle tree. There are only a few grey areas, such as the definition of calldata types. These could arguably be either but are best categorised as constants because they will actually never be dependent on the details of a deployment.

changes accommodated