[feat] endpoint for create/edit/delete collection

[Jipperism]

Add a controller + endpoint for managing/creating a collection, instead of only being able to do so through the hypercerts endpoint.

Refactor the hyperboards endpoint to reuse the same code where possible.

[Jipperism]

@holkexyz @bitbeckers I'd also expect this involves updating the hyperboard endpoint, so that you are only allowed to add/remove existing collections to a hyperboard through there, instead of creating new ones on the fly.

[holkexyz]

@Jipperism a use case would be that, for instance, GainForest could use the endpoint to manage a GainForest collection from their frontend? Have they expressed that they would use this or is it advisable to add it now, in case someone would use it in the future?

[Jipperism]

@holkexyz Yes, correct. Currently they're able to retrieve a collection through our graphql api, but to edit/create one they need to use the hyperboard endpoint. It's confusing as they have to specify display sizes etc, which they never use.

If we switch to separate forms, making the logic in the frontend so that we can make all calls to the hyperboards endpoint will be more effort and bug-prone than splitting up the endpoint into /hyperboards and /collections. That will make the collection form communicate with the collection endpoint, and the hyperboard form with the /hyperboard endpoint.

Honestly, it's the right thing to do in every way, the only reason we didn't being that the old 'collection' form was a proof-of-concept :)

[holkexyz]

Great, agreed