Issue Summary

This is the same limitation as Jira Server(JIRAAUTOSERVER-833)
Project admins, who are not product admins, cannot update Multi-Project Automation rules even when they are project admins to all the projects covered in the automation rule or owner of the rules.

When the project admin goes to update the rule, they will see the rule's configuration but will be in 'Read-Only'.

Steps to Reproduce

1. Create a secondary account that is not a jira-admin or site-admin, but is a project admin for 2 company-managed projects (need* Administer Projects* and Browse Projects permissions)
2. Create an Automation Rule with Multi-Project Scope, scoped out for the 2 CMP projects
3. For Who can edit this rule select Specific admins and select the secondary account(Project Admin)
4. Ensure that in Global automation > ... *> *Global configuration that the user is in one of the groups to Allow project administrators to manage project rules
5. Log in with the secondary account(Project Admin)
6. Navigate to one of the projects and go to Project Settings > Automation and try to edit the automation rule.
7. It will say "READ-ONLY" at the top despite having access

Expected Results

If a user is a project admin of all the projects of a Multi-Scope Automation rule, they will be able to update the rule via Project Settings > Automation.

Actual Results

When the project admin/Rule Owner goes to Project Settings > Automation and selects the multi-project rule, they are only able to access it in read-only mode