Clearly write endianness of contract/transaction hashes in the user-facing output (log)

Is your feature request related to a problem? Please describe.

I'm always frustrated when user sees contract/transaction hash in the log and can only ask "what the endianness?". And even more frustrated when actual endianness differs from other Neo-based software like https://github.com/nspcc-dev/neo-go/.

Describe the solution you'd like

1. decide what E to use. Neo Go uses LE, so it's worth to do the same
2. write all user facing prints in this E, don't diverge formats
3. clearly write what is printed to be completely sure (e.g. "contract/transaction (LE)": "...")

with this, observer will definitely know what he sees. Even if he need an opposite E, there is neo-go util convert utility to help

Describe alternatives you've considered

i dont see ones

Additional context

take contract/transaction from NeoFS chain auto-deployment log and go neo-go query tx it 🏁

Start by locating the user-facing contract and transaction hash output, then compare it with the NeoFS chain auto-deployment log and neo-go query tx. Decide and document the endianness, update the relevant prints consistently, and verify that each displayed hash clearly labels its endianness.