client,providers: add storj DCS as provider option

[stefanbenten]

• I added CHANGELOG entry for this change.
• Change is not relevant to the end user.

Changes

• Adding Storj Provider
• Fixed import ordering for some touched files to make them consistent
• Fixed some smaller items in the README.
• Added the missing error checks in the cfggen script.

Verification

• Compiled and ran it locally, worked fine.
• Still working on adding the "Local Test Network" to ensure full functionality.

[brancz]

I have practically no experience with storj, but one of the first things it says in the docs is that it’s S3 compatible, so I wonder what a direct integration does better than using the existing S3 integration?

[stefanbenten]

Hello @brancz, thank you for looking at this!

The native integration offers several advantages over the S3 compatible gateway.
One of them being performance (cuts out the proxy/gateway) and the other important one being client side encryption rather than have it be done server side.

[brancz]

This generally looks good to me. I wonder though if you'd be up for maintaining this, as if there are problems I don't think any of us have enough knowledge about Storj to be helpful in a meaningful way.

Would you be up for that?

[stefanbenten]

Thank you a lot @brancz !

I am more than happy to maintain the integration, let me know if there is anything further needed!

[GiedriusS]

Are there any containers that we could run to start a new storj object storage? Or is it a proprietary product? It would be ideal to have some integration tests.

[GiedriusS]

It's not necessary to check for err here in Log() calls.

[stefanbenten]

This was mainly a thing that my environment complained about. I saw it wasnt needed after all, but thought it might be a little cleaner anyway.