Add a permission for supervisor to edit contacts

[mythilytm]

Description

This PR adds a permission check for supervisors to edit in-progress contacts

• Defined new SUPERVISOR_EDIT_CONTACT action in actionsMaps and updated canPerformActionOnContact to include SUPERVISOR_EDIT_CONTACT permission check.

Checklist

• Corresponding issue has been opened
• New tests added
• Feature flags / configuration added

Other Related Issues

None

Verification steps

AFTER YOU MERGE

1. Cut a release tag using the GitHub workflow. Wait for it to complete and notify in the #aselo-deploys Slack channel.
2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P

[stephenhand]

I thought we were going to add an extra permission action to the framework rather than just hardcoding supervisors having permission? Then we would do a can(...) check on this permission, and if that passes OR one of the existing hardcoded checks passes, then they can edit

[stephenhand]

Suggested change

	user.roles.map(role => role === 'supervisor')
	Boolean(user.roles.find(role => role === 'supervisor'))

[stephenhand]

LGTM after the tests are fixed