CHI-3207: Replace section specific permissions with generic ones that cover all section types

[stephenhand]

Description

• Replaced all the add / edit permissions for specific case sections with addCaseSection and editCaseSection
• Refactored ViewCaseItem to use redux hooks rather than mappings

Checklist

• Corresponding issue has been opened
• New tests added
• [n/a] Feature flags added
• [n/a] Strings are localized
• Tested for chat contacts
• Tested for call contacts

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

[GPaoloni]

LGTM!

I assume there's an HRM PR this one depends on (hrm needs to be in place before this is deployed I think)?

[stephenhand]

LGTM!

I assume there's an HRM PR this one depends on (hrm needs to be in place before this is deployed I think)?

Yes, this version will be dependent on the new HRM version being deployed (but not vice versa) - I think you already approved that PR