Extend token instance metadata parsing functionality

[vbaranov]

Motivation

Multiple token instance metadata fetching errors

Changelog

New fetching token instances covered:

• parse IPFS links, if protocol is in diverse case (IPFS://, IpFs:// etc)
• fetch URI, if token URI directly passed to fetch_json/2
• fetch URI, if token URI in quotes directly passed to fetch_json/2
• fetch URI, if CIDv0 IPFS id directly passed to fetch_json/2
• process an error, if whatever response code returned, but error message contains execution reverted text
• process an error, if whatever response code returned, but error message contains VM execution error text

Checklist for your Pull Request (PR)

• I added an entry to CHANGELOG.md with this PR
• If I added new functionality, I added tests covering it.
• If I fixed a bug, I added a regression test to prevent the bug from silently reappearing again.
• I checked whether I should update the docs and did so by submitting a PR to https://github.com/blockscout/docs
• If I added/changed/removed ENV var, I submitted a PR to https://github.com/blockscout/docs to update the list of env vars at https://github.com/blockscout/docs/blob/master/for-developers/information-and-settings/env-variables.md and I updated the version to master in the Version column. Changes will be reflected in this table: https://docs.blockscout.com/for-developers/information-and-settings/env-variables.
• If I add new indices into DB, I checked, that they are not redundant with PGHero or other tools