CHI-3566: Add 'nobody' condition test coverage for permission rules

[Copilot]

Description

Enhanced permission unit tests to cover the nobody condition—a user-based condition that always evaluates to false, effectively denying all permissions. Tests verify denial behavior across all permission target kinds.

Test coverage added for:

• CaseActions
• ContactActions
• ProfileActions
• ProfileSectionActions
• ViewIdentifiersAction
• ContactFieldActions

Key test scenarios:

• nobody alone always denies access
• nobody combined with other conditions in same set still denies
• nobody in one condition set can be overridden by another condition set evaluating to true
• ContactField-specific: nobody without field condition doesn't restrict fields (follows field-specific permission logic)

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 permission unit tests:

cd plugin-hrm-form
npm test -- --testPathPatterns=rules.test.ts

All new nobody condition 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

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.