feat: filter addresses and name for phishing

[0xNumlock]

The NFTX JS Api was returning scam/phishing tokens - this PR filters them out as per the lists taken from https://github.com/scamsniffer/scam-database

[jackmellis]

A slight issue with this is fetchUserCollections isn't the only source of collection data - in fact I'm not sure if it's even being used in v3 now!

Currently the API is actually getting the list of collections from the ERC721/ERC1155 subgraphs and then pulling/caching the metadata for each one from reservoir (potentially not the most efficient method but a problem for another day), and sometimes it's getting the list of collections by just checking the vault, sometimes it's being given a list of addresses and cross referencing with what vaults there are, etc.

I think the filtering should either happen just in the api repo here: https://github.com/NFTX-project/nftx-api/blob/a6e18a88f22054b8ca6554ff5b84e38ebbeba519/src/application/collections/getCollections.ts#L97 or in both (which would require exposing the list of 0x/domains somewhere for both to consume)

[0xNumlock]

A slight issue with this is fetchUserCollections isn't the only source of collection data - in fact I'm not sure if it's even being used in v3 now!

Currently the API is actually getting the list of collections from the ERC721/ERC1155 subgraphs and then pulling/caching the metadata for each one from reservoir (potentially not the most efficient method but a problem for another day), and sometimes it's getting the list of collections by just checking the vault, sometimes it's being given a list of addresses and cross referencing with what vaults there are, etc.

I think the filtering should either happen just in the api repo here: https://github.com/NFTX-project/nftx-api/blob/a6e18a88f22054b8ca6554ff5b84e38ebbeba519/src/application/collections/getCollections.ts#L97 or in both (which would require exposing the list of 0x/domains somewhere for both to consume)

https://github.com/NFTX-project/nftx-api/pull/20