Developer contribution process

[chriskapp]

Currently it is possible in Fusio to create a developer role for the backend which restricts access s.

A developer can create in this role all operations, schemas and actions to solve a specific task and has no access to the complete backend. After the developer is done we need an option to move those entities back to the main category so that it can be used in the live API.

We may need to build a small process where the developer has a contribute button, which submits all entities to a contribute queue which then can be accepted by an admin user. At the admin view we only need to show the entities and maybe also an option to reject the changes with a message that something is missing.

We could also add a longer description to the category which we could display at the backend where the admin can describe the exact tasks.