fix(payment-detection): differenciate decentralized network case

[alexandre-abrioux]

This is a fixup for #1262 and #1265

Context

When using TheGraph decentralized network, different GQL queries can target different indexers. For consistency, we can ask to target only indexers that have processed specific blocks using a block filter.

For more info, see here or here, look for number_gte in these pages.

Description of the change

When we don't have the data for which minimum block an indexer should have processed, we must set a default value. After several unsuccessful tries, here is what I've found regarding generating a default value that works with both a normal TheGraph Node and the decentralized gateway:

Block Filter	TheGraph Node	TheGraph Gateway (decentralized)
undefined	✅	❌ Invalid query: Failed to determine block constraints.
null	✅	❌ Invalid query: Failed to determine block constraints.
empty object: {}	❌ Invalid value provided for argument block: Object({})	✅
default to zero: { number_gte: 0 }	✅	❌ Invalid query: Requested block before minimum startBlock of manifest: 0

This shows that no default value is compatible with both setups. We need to differentiate between both. I've added a new decentralizedNetwork boolean option that auto-populates depending on the URL value and allows to distinguish between both cases.

[coveralls]

coverage: 87.089%. remained the same
when pulling 0a550d0 on fix-payment-detection-decentralized
into 28cf4b6 on master.

[benjlevesque]

Wow, great find... Strange that TheGraph doesn't expect the same input on hosted vs Network 🤔 I wonder if this is intentional.

I'd prefer an approach where the complexity related to the Network is kept centralized in the client , and abstracted in the info-retriever, but your solution works just fine! For the record, here's what I suggest, but not a blocker
Great work