[Feature Request] Make `AccountAddressParseError` more descriptive

Currently when we fail to parse `AccountAddress`, the error is simply `AccountAddressParseError` without an error message. It would be very helpful to add an `error` field to this error and provide the reasons for parsing failure.

Start by locating the AccountAddress and AccountAddressParseError definitions and tracing the AccountAddress parsing entry point and its failure paths. Confirm how each parsing failure is represented; done means the error carries an error message describing the parsing reason.

Written by the indexing model from the issue text.