Minor improvements to error messages

[JustinAzoff]

When trying to reproduce an analyzer issue I often see messages like:

[fatal error] terminating with uncaught exception of type spicy::rt::ParseError: &size amount not consumed (./analyzer/asn1.spicy:123:16)
[fatal error] terminating with uncaught exception of type hilti::rt::RuntimeError: more than max of 8 bytes for conversion to integer (./analyzer/asn1.spicy:82:12)

It would be nice of those messages were more like

[fatal error] terminating with uncaught exception of type spicy::rt::ParseError: &size amount not consumed. 
 Expected 100, got 85 (./analyzer/asn1.spicy:123:16)
[fatal error] terminating with uncaught exception of type hilti::rt::RuntimeError: more than max of 8 bytes for conversion to integer: 16 (./analyzer/asn1.spicy:82:12)

[awelzel]

Piggy-backing, a few days ago I was tempted to open a similar issue for switch (expr) not including information for the no matching case error:

"failure_reason":"no matching case in switch statement (<...>/QUIC.spicy:174:3-183:5)"

Mostly convenience during development, but depending on the switch and involved types, potentially interesting to pivot on parser errors in live deployments, too.