Fixes #5564 Profile editor content moderation workflow permissions

[tadean]

Currently, Profile Editors lack permission to use content moderation workflows. This means that if their person node has a moderation status, they are unable to edit it. This PR proposes that the Profile Editor role receive permission to work with content moderation.

Description

This PR adds permissions to az_profile_editor to work with content moderation workflows.

Release notes

The az_profile_editor role now has permission to use content moderation workflows on their associated person node.

Related issues

#5564

How to test

• Visit /admin/config/workflow/workflows/manage/editorial
• Enable the content moderation workflow for the Person content type
• Create two person nodes. Give one of them your own netid
• Edit both person nodes, edit one aspect, and save in draft moderation status
• Verify that the author of each node is the user 1 superuser
• Provision a CAS account for your netid. Give it the Profile Editor role and no other
• Login as your CAS account
• Verify that you can edit the person node with your netid
• Verify that on the edit form you see the edit that was present in the draft
• Verify you can publish the draft (todo: determine if this is desired)
• Verify you cannot edit the person node that does not have your netid

Types of changes

Arizona Quickstart (install profile, custom modules, custom theme)

• Patch release changes
  • Bug fix
  • Accessibility, performance, or security improvement
  • Critical institutional link or brand change
  • Adding experimental module
  • Update experimental module
• Minor release changes
  • New feature
  • Breaking or visual change to existing behavior
  • Upgrade experimental module to stable
  • Enable existing module by default or database update
  • Non-critical brand change
  • New internal API or API improvement with backwards compatibility
  • Risky or disruptive cleanup to comply with coding standards
  • High-risk or disruptive change (requires upgrade path, risks regression, etc.)
• Other or unknown
  • Other or unknown

Drupal core

• Patch release changes
  • Security update
  • Patch level release (non-security bug-fix release)
  • Patch removal that's no longer necessary
• Minor release changes
  • Major or minor level update
• Other or unknown
  • Other or unknown

Drupal contrib projects

• Patch release changes
  • Security update
  • Patch or minor level update
  • Add new module
  • Patch removal that's no longer necessary
• Minor release changes
  • Major level update
• Other or unknown
  • Other or unknown

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My change requires release notes.

[tadean]

Todo:

• Determine desired scope of profile editor permissions
• Add potential new permission view associated unpublished content that mimics the function of view own unpublished content (profile editors generally will not own their node)