Create `non-standard` class to handle non-standard but common token read methods

Per the conversation [here](https://github.com/MetaMask/controllers/pull/834#discussion_r877199312), we are failing to properly return values for contracts that contain methods like `name()`, `symbol()`, `tokenURI()` and `decimals()` that do not fully conform to one of the 3 major token standards we currently support (ERC20, ERC721, ERC1155). We should create a backstop to return these values regardless of whether they are part of a standard contract.