LPS-32269

Initial fix:
Users with DELETE permission on category should also have DELETE permission on threads. It should also apply to SUBSCRIBE permission.



After further investigation I found that categories and folders check parents for permission on all actions. If a parent category/folder has a permission for an action, all children categories and folders (NOT including file entries and threads) under that parent will have that permission.

The exception is when permission.view.dynamic.inheritance=true. This means we should inherit VIEW permissions following the 'dynamic inheritance' rule.

I've attempted to make parent-child relationships consistent across the board:
- if a category has a permission, the children (both threads and categories) will also have that permission
- if a folder has a permission, the children (both file entries and folders) will also have that permission
- if a wiki node has a permission, the children (wiki pages) will also have that permission
- if a wiki page has a permission, the children (wiki pages) will also have that permission

Dynamic inheritance is not being checked on categories and folders every time. It is only checking when action=VIEW! This should not be the case because it creates the situation where a user will not be able to VIEW content, but still able to perform other actions on it (DELETE, MOVE, EDIT, etc..). This creates a false sense of security. If dynamic inheritance denies access to VIEW it should also deny access to all other actions.