Refactor logic of chainID and chainIdentifier.

[0xsarvesh]

Mosaic chains supports readable chain identifier like ropsten, ethereum etc for origin chain. However, different part of code requires chainID for instance deployment of anchor needs remoteChainID which is uint256.

For developer, it's a pain point and confusing what originChain means. Both chainIdentifier and chainID is required in the codebase.

This ticket is about defining and implementing a clear approach to keep both terminology.

Possible approach: Code should only use chainIDs everywhere and at commander layer chain Identifiers should be converted to chainIds.