show more context when deserialization errors occur

[cbeck88]

this adds a new pattern for handling errors when json bodies don't match the rust schema, so that the errors include more detail of what didn't deserialize. this helped me figure out what was wrong when the get_assets endpoint failed when monad was added

Added feedback

[extremeandy]

Another idea could be to just use tracing and log the body, if this is more for debug.

[cbeck88]

Another idea could be to just use tracing and log the body, if this is more for debug.

yeah, that's a good idea too, and it's less noise in the API.

happy to rewrite the PR that way

[extremeandy]

Another idea could be to just use tracing and log the body, if this is more for debug.

yeah, that's a good idea too, and it's less noise in the API.

happy to rewrite the PR that way

That'd be my preference but not sure what others think :)

[cbeck88]

done, lmk what you think

[cbeck88]

rebased on master and resolved conflicts

[cbeck88]

CI failure looks unrelated:

0s
Run cargo fmt --all --check
cargo fmt --all --check
shell: /usr/bin/bash -e {0}
env:
CARGO_HOME: /home/runner/.cargo
CARGO_INCREMENTAL: 0
CARGO_TERM_COLOR: always
CACHE_ON_FAILURE: false
Error: An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/bpx-api-client/bpx-api-client/rust'. No such file or directory
Run cargo fmt --all --check
cargo fmt --all --check
shell: /usr/bin/bash -e {0}
env:
CARGO_HOME: /home/runner/.cargo
CARGO_INCREMENTAL: 0
CARGO_TERM_COLOR: always
CACHE_ON_FAILURE: false
Error: An error occurred trying to start process '/usr/bin/bash' with working directory '/home/runner/work/bpx-api-client/bpx-api-client/rust'. No such file or directory