Improve the publication process

- [x] #1075
- [x] #1104
- [x] #1115
- [x] graasp/graasp-builder#1355
- [x] graasp/graasp-builder#1253
- [x] graasp/graasp-builder#1296
- [x] #1228
- [x] #1231
- [x] #1270
- [x] #1275
- [x] refactor the validateItem by using the Strategy pattern instead of the switch
- we could also try to refactor a bit the _post method
- [ ] enhance the way the user can edit other sibling or children items without having to close the publication page
- maybe the user should see the siblings and children directly in the publication page ?
- [ ] display the names of the invalid items
- [ ] ensure a children can't be published if the parent is already published (in the backend).
- [ ] handle the existing published children when publishing a parent
- I think the easiest way is to remove the published children when publishing its parent ? The user should be informed of that action in the front.
- [ ] validate item's description using a moderation solution. Check this analyse graasp/graasp#1243.
- [ ] revalidate an updated published item to ensure the content is still valid.
- if it is not the case anymore, we should catch this
- display a warning in the frontends and the item remains published
- automatically revalidating the changes
- [ ] improve the backend's validation
- revalidate only for a set of columns (no need to revalidate for boolean fields for example)
- an improvement could be to only validate the changed field.
- if we remove the invalidated item, the state will be unpublished and not invalid because the itemvalidation entry is removed when the item is deleted...

Process of publication: