Add comprehensive test coverage for contactField permission rules

[Copilot]

Description

Adds test suite for contactField target kind permission evaluation, covering edge cases in field-specific condition filtering logic.

Test Coverage

• Default allow behavior: Fields without explicit field conditions are permitted by default
• Global conditions: Non-field-specific conditions (everyone, isSupervisor, isOwner) apply uniformly across all fields
• Condition filtering: Field-specific conditions are correctly filtered when evaluating permissions for a given field
• Conflicting field conditions: Condition sets containing multiple field conditions for different fields are properly filtered out, with other condition sets able to override

48 test cases added (24 per action: viewContactField, editContactField)

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

Run the test suite:

cd plugin-hrm-form
npm test -- src/___tests__/permissions/rules.test.ts

All 303 tests should pass.

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

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.