Add more simple `draft` and `publish` versioning mode

Summary With versioning stabilized, I think it is time to discuss possible improvements to make it more accessible for more basic use-cases that only need simple draft and publish architectures. The design with multiple branches certainly has many good use cases, but I think more simple use cases should also not be forgotten. That is why I propose not to change the current implementation and make it less complex, but rather to add additional configuration options to it. • Our requirement would be to just have 2 branches. One called published and one called draft for example. • If you open an item, you would usually be in the draft branch, so changes that you make are not automatically published. • It would be good to just have a very obvious publish button next to the save button for example. Basic Example _No response_ Motivation I think this workflow would be very good for our users to prevent them to accidentally make changes, that should not be pub…