(Re)Move screen action trigger

Currently a lot of screen definitions have action triggers included to have the user do something in relation to the object (entity record) of the screen. 

The action trigger must be removed from the screen and added to the object's ActionMenu to create a unified user experience across the screens in all applications. In addition to that, it is easier to do permission conditions in a menu than in a screen. A menu-item just needs the condition, while a screen - on top of the condition - needs a section/widget/etc. to comply with the project's best practices.