Change `funding.json` format / parsers to play well with fundingjson.org

[shielded-nate]

Hi, I just discovered Drips (via revisiting Radicle), then discovered fundingjson.org which appears to be an independent specification for funding.json conventions. That specification site links to dir.floss.fund, and this appears to be more general purpose than the crypto-ecosystem.

I would love it if both conventions played well together, so that projects have the freedom / option to participate in Drips and/or other general purpose funding schemes from the other schema.

I filed funding-manifest/fundingjson.org#8 over there with an in-depth description to compare the efforts and motivate unifying them. Please check that out.

IIUC, the fundingjson.org schema doesn't need to be altered to support shoe-horning crypto stuff into that format, so it would be on Drips tooling to be able to handle that shoe-horning and (a subset of) that schema.

The goal is this user story:

As a FLOSS project, we decide to publish a funding.json that enables transfers to our org's bank account, our paypal account, and our Ethereum address, especially because we're a lean non-profit project and rely on donations through multiple channels and losing out on any of those three payment options would significantly reduce our operating revenue.