Work for this was redirected to https://slidewiki.atlassian.net/browse/SWIK-1031 as short-term requirements changed

I did some testing today to review how the deck service efforts work with platform:

1. root deck selected, user cannot fork it (e.g. restricted deck)

   1. "add new slide/deck" should be disabled, "edit" as well

   2. when clicking "edit" user is alerted and brought back to view, not very user friendly

2. deck tree component, user cannot fork root deck (e.g. restricted deck)

   1. the "fork" button gets enabled/disabled depending on selected subdeck, should be only dependent on root of deck tree

   2. in direct children of root, options ( three dots ) should not be there at all as none of them can be performed

   3. in direct children of root, rename should also be disabled

   4. when selecting direct children of root deck, in content panel the buttons for edit, add slide/deck, duplicate, delete should also be disabled since no fork is allowed for root deck

   5. in indirect descendants of root, current deck-service API needsNewRevision / forkAllowed / editAllowed is not enough, we need to check if editing a deck is allowed in the context of the deck tree, because for example if a user tries to fork a deck they have rights to fork, they also need to have edit rights to the deck parent, and so on. This applies to determining (b) and (c) for descendants (pending deck-service implementation)

The deck-service infers authorized users from already made changes on the deck/slides - use-case is here that contributors of a deck were not blocked when a deck become restricted.
Showing a list of such users is optional and will not be done in this ticket/sprint.

I had to make changes in the user-service as well - have to be merged into master as well when this ticket is finished.
As there were database changes the following have to be executed on the mongodb:

General discussion is now at https://slidewiki.atlassian.net/wiki/display/SWIK/Realize+edit+rights
Decisions from there will be implemented here (frontend part)