Pretty manifest compiler error reporting

[lrubasze]

Summary

This PR adds pretty compiler error reports for more clarity.
Examples:

or

Details

Chosen annotate-snippets crate to pretty print faulty manifest snippets.
There are also some other libs, but they are not maintained or are not widely adopted.
This crate is used by cargo, which was decisive argument to pick it up.
Each of the compiler errors: LexerError, ParserError, GeneratorError has its own error diagnostic function, which:

• analyses the error
• and prepares a manifest snippet accordingly

More ideas:

• Add suggestions in the footer of the report, eg.
  invalid Ident specified 'CALL_METHODS', maybe you ment: 'CALL_METHOD'
• provide more info basing on nested errors such as AddressBech32DecodeError or ParseNonFungibleLocalIdError
  instead of generic error message such as:
  error: invalid global address 'some_address'
• prepare more precise message for aliases (eg. Bytes, Ok)
  we could print:
  error: expected value of type String, found Bytes (alias of Array)
  instead of:
  error: expected value of type String, found Array

Testing

Respective tests added.
Each test consist of 2 files:

• *.rtm manifest file with some error
• *.diag file with expected compiler output
  These files don't look good in Github, the best is to inspect them with cat command in terminal.
  Others use *.svg files, but I thought it's better to keep it simple.

Update Recommendations

For dApp Developers

Enjoy beautiful compiler error reports 🥂

For Internal Integrators

Maybe worth integrating with anything that uses raw manifest *.rtm files

[dhedey]

Really nice work! This is looking great. I love the attention to detail and clear error messages.

Most of my comments are minor suggestions/nitpicks, though there are one or two bugs that could be fixed too.