PlutusData::to_cardano_node_format()

[rooooooooob]

Returns the same datum but with the encoding details changed so that it will match cardano-node/CSL/Lucid

This is only in cases where dealing in raw bytes and/or from_cbor_bytes() is somehow not possible, as that solution is 100% fool-proof with any tool always for calculating hashes.

Fixes #356

[SebastienGllmt]

Perhaps this should be mentioned in the docs if we think this is a common issue?

[rooooooooob]

@SebastienGllmt I'm not sure if we should be encouraging this in situations where it's avoidable. It's not good practice to hope that every little bit will line up when creating datums from scratch using a specific tool. It's much better to use PlutusData::from_cbor_bytes() on the bytes created with whatever other tool/on-chain data you're working with and know for sure you won't run into issues regardless of the tool. We already have a CBOR section in the docs as of #345. I could expand upon it if needed or put even more emphasis on from_cbor_bytes(). It already mentions how it can make the hash change if 1 thing is encoded differently and that using types created from the cbor bytes using CML avoids these issues.