BridgeMessageId=>TokenMessageId

[xiaoch05]

To avoid the type conflict of this update.
paritytech/parity-bridges-common#1152

[xiaoch05]

@hackfisher the docs is here https://github.com/darwinia-network/darwinia-common/blob/master/frame/support/src/lib.rs#L103-L107.
and for sub<>sub bridge, it combines laneid and nonce. We leave 4 bytes to indict chainid in the future.

and this message_id also used in mapping-token-factory at https://github.com/darwinia-network/darwinia-bridge-sol/blob/master/contracts/mapping-token/contracts/darwinia/DarwiniaMappingTokenFactory.sol#L154

[hackfisher]

Since this is only used in wormhole and token protocol, please rename it to TokenMessageId or TokenBridgeMessageId, and also related traits & methods.

	fn latest_message_id() -> BridgeMessageId {
		let nonce: u64 =
			BridgePangolinMessages::outbound_latest_generated_nonce(PANGORO_PANGOLIN_LANE).into();
		nonce_to_message_id(&PANGORO_PANGOLIN_LANE, nonce)
	}

[hackfisher]

LGTM, not sure whether we need to update the types.json for pangolin and pangoro.

[xiaoch05]

LGTM, not sure whether we need to update the types.json for pangolin and pangoro.

The types.json is updated in ./node/runtime/pangolin/types.json. @AurevoirXavier do we use the same type.json file as pangolin in pangoro?

[aurexav]

LGTM, not sure whether we need to update the types.json for pangolin and pangoro.

The types.json is updated in ./node/runtime/pangolin/types.json. @AurevoirXavier do we use the same type.json file as pangolin in pangoro?

Yes, there is no need to update for pangoro.

[boundless-forest]

Seems good. A question feedback left.

[boundless-forest]

I am curious about this writing style, Can we change it to "TokenMessageId": "[u8; 16]",?