Adds more descriptive and helpful error messages to the NFT contracts and txs

[joshuahannan]

Closes: #232

Based on guidelines in onflow/docs#795

Description

• Updates all error messages to include more information and relevant data about the error if possible
• Updates CLI commands for C1.0

---

For contributor use:

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Re-reviewed Files changed in the Github PR explorer

[bjartek]

Imho resolving a view should never
Panic. Return nil.

[joshuahannan]

Agreed! I'll remove that. Good catch!

[sisyphusSmiling]

Really like the detailed error message, thanks for fixing these up! My main suggestion is not a blocker, but it would be great to see consistent formatting e.g. some messages wrap values in () or <> and others prefix values with =. In reality, this probably more of a preference/nitpick

[joshuahannan]

@sisyphusSmiling Good point! I'll look through and make sure they are consistent. The only time I use <> is when I am dealing with types because that is usually what they are contained in in the code, so I thought it would make sense to be consistent with that. But agreed about using = vs (). I'll find a consistent format.