Add new contributions permission

[duartegalvao]

Adds a new contributions permission for managing event contributions

[ThiefMaster]

Looks good, one thing I'd test is whether the "undo" from the small popup you get when unassigning the session from an already-scheduled contribution (removing/changing the session unschedules id) still works. Because I think that might send a request to a timetable-related endpoint...

Edit: Indeed, the undo button there fails, because it POSTs to RHTimetableREST.

[ThiefMaster]

RHAssignProgramCodesContributions needs to either check the new permission as well or alternatively hide the "Assign program codes" button on the contributions list when you do not have full management permissions.

[ThiefMaster]

"Send email" works fine, but "Authors list" -> "Send email" doesn't, since the latter uses are more generic endpoint which still checks for full management privileges.

[ThiefMaster]

"Assign new session" and "Add new track" fail (as expected -> should be hidden).
Assigning an existing one works fine as expected.

[ThiefMaster]

Should the "publish/draft contributions" toggle be accessible with this permissions (currently it is), or should that require full management privileges? I'm leaning towards the latter since that goes beyond just managing (some) contributions...

[duartegalvao]

Should the "publish/draft contributions" toggle be accessible with this permissions (currently it is), or should that require full management privileges? I'm leaning towards the latter since that goes beyond just managing (some) contributions...

Makes sense, I agree. For the jacow use-case all they need is to be able to edit titles/authors of contributions, so for this it wouldnt matter

[duartegalvao]

"Assign new session" and "Add new track" fail (as expected -> should be hidden). Assigning an existing one works fine as expected.

I think I will just disallow any session/track assignment - imo those should be in a separate permission ("timetable" and "programme" respectively)

[ThiefMaster]

That change wasn't correct, it's a management check on the contribution so there we need to check for full management access. Anyway, I reverted this in 986469c.

ValueError: permission 'contributions' is not valid for 'Contribution' objects