[Feature Request] Keep the finer granular error code for MiscellaneousError about move

[tnowacki]

Pulling from @sblackshear's detailed answer on discord (Thanks Sam!)

"For some historical context, I believe we used to support a much broader set of error codes, but were having difficulty with error codes committing to implementation details of the Move VM or the adapter. The current error behavior is a reaction to this experience. Error behavior is part of the VM spec, so it's important to keep it as simple/minimal as possible. That is (unfortunately) at odds with devex, but as Todd says, the intention is that this belongs in tooling outside the VM or in a layer above like the adapter"

In short, this isn't the purpose of VMStatus, as an adapter, you can use VMError as much as you want, and report this back to the developer as you see fit. The VM doesn't guarantee being stable enough to always return the same type checking error. It guarantees Yes/No answers on verification. And then guarantees the position for any Move Abort

[tnowacki]

Closing for now as it won't be something that is changed. But happy to help with sorting out any information that is missing in VMError or for strategies in logging that error

[areshand]

thanks for the detailed answer.