CHI-3566: Add contact field permission support

[stephenhand]

Description

Adds support for loading contactField type permissions from the backend
Makes fields without view permissions hidden
Makes fields without edit permission read only

Checklist

• Corresponding issue has been opened
• New tests added
• Feature flags added
• 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

[stephenhand]

@copilot Enhance the rules.test.ts in plugin-hrm-form to include specific tests for permissions with the contactField target kind

The additional tests should cover addtional scenarios including, but not limited to:

• fields being checked that are not specified by a 'field' condition in any condition set are always allowed
• condition sets that have no field condition will allow any field if they evaluate to true
• if there are condition sets with no field condition that evaluate to false, but there are no condition sets that have a field condition matching the field being checked, the action should be allowes
• Multiple field conditions in the same set specifying different fields means that condition set will always evaluate false, but can still be overridden by other condition sets evaluating to true in the usual way

[Copilot]

@stephenhand I've opened a new pull request, #3912, to work on those changes. Once the pull request is ready, I'll request review from you.

[stephenhand]

@copilot Enhance the rules.test.ts in plugin-hrm-form to include specific tests for permissions with the contactField target kind

The additional tests should cover addtional scenarios including, but not limited to:

• fields being checked that are not specified by a 'field' condition in any condition set are always allowed
• condition sets that have no field condition will allow any field if they evaluate to true
• if there are condition sets with no field condition that evaluate to false, but there are no condition sets that have a field condition matching the field being checked, the action should be allowes
• Multiple field conditions in the same set specifying different fields means that condition set will always evaluate false, but can still be overridden by other condition sets evaluating to true in the usual way

[Copilot]

@stephenhand I've opened a new pull request, #3913, to work on those changes. Once the pull request is ready, I'll request review from you.

[stephenhand]

@copilot enhance permissions unit tests to add coverage for the new 'nobody' condition

[Copilot]

@stephenhand I've opened a new pull request, #3917, to work on those changes. Once the pull request is ready, I'll request review from you.

[gpaoloni]

Looks good to me! Only having to change ContactDetailsSectionForm.tsx for all the changes to take effect is lovely to see.