feat: add studio write access validation

[germanolleunlp]

Add studio write access validation

Ticket: https://jira.2u.com/browse/ACADEMIC-16359

Merge checklist:
Check off if complete or not applicable:

• Version bumped
• Changelog record added
• Documentation updated (not only docstrings)
• Fixup commits are squashed away
• Unit tests added/updated
• Manual testing instructions provided
• Noted any: Concerns, dependencies, migration issues, deadlines, tickets

[ashultz0]

needs a changelog entry and update of version number, probably to 3.5.0

thoughts about organization you can take or leave

also it might need the decorator that actually requires and decodes a user on the view calls

[germanolleunlp]

needs a changelog entry and update of version number, probably to 3.5.0

thoughts about organization you can take or leave

also it might need the decorator that actually requires and decodes a user on the view calls

💹 done

[ashultz0]

this is a weird python resource leak technicality

in super.setup it makes self.accessmock and starts it, let's call that mock1
then here you reassign self.accessmock to a new mock and start it, that's mock2
there is no longer any reference available to mock1, self.accessmock is now mock2

in teardown we tear down mock2. mock1 is never torn down.

I don't think that mocks really leak anything significant especially if you never start them so this is just something to notice. Fixing it would just be not calling super setup or delegating mock creation into a function which reads self.can_change_summaries or a million other methods.

[ashultz0]

this is worth knowing about but not a blocker to merge I think

[germanolleunlp]

Thanks!