Better error handling, pattern matching instead of conditional flow

[0xDmtri]

Description

Improved error handling and exhaustive handling of all the possible error codes. In original implementation only two variants of enum were handled in conditional manner (which is not robust in this case). The proposed usage of pattern matching via "match" case is a better way of handling errors. I have proposed a new enum variant for an Error that returns the standardized error code instead.

Let me know if there are any further suggestions for improvement.

Checklist

• [+] Formatted code using cargo fmt --all
• [+] Linted code using clippy
  • [+] with reqwest feature: cargo clippy --manifest-path influxdb/Cargo.toml --all-targets --no-default-features --features use-serde,derive,reqwest-client -- -D warnings
  • [+] with surf feature: cargo clippy --manifest-path influxdb/Cargo.toml --all-targets --no-default-features --features use-serde,derive,hyper-client -- -D warnings
• [+] Updated README.md using cargo doc2readme -p influxdb --expand-macros
• [+] Reviewed the diff. Did you leave any print statements or unnecessary comments?
• [+] Any unfinished work that warrants a separate issue captured in an issue with a TODO code comment

[msrd0]

Did you intentionally or accidentially close this PR? If the former, would you be ok if we used your changes as a base for a new PR?

[0xDmtri]

Did you intentionally or accidentially close this PR? If the former, would you be ok if we used your changes as a base for a new PR?

Hey, intentionally because of the mess I made there haha. I am on track of redesigning my previous logic into something better. I will make a new PR today in the evening. Sounds good?

[msrd0]

Sounds good :+1: