Issue Summary

Ability adjust the priority of the automation rules based on the requirement.

Steps to Reproduce

Currently, in A4J there is no built-in mechanism (system property, REST API, or configuration setting) to change the default priority assigned to specific event types in the A4J automation queue. The priority value is hardcoded internally by the A4J plugin when events are serialized into the queue table. [General troubleshooting guide for Jira automation | Automation for Jira Cloud and Data Center | Atlassian Documentation|https://confluence.atlassian.com/automation110/general-troubleshooting-guide-for-jira-automation-1627459289.html]

select * from "AO_589059_AUTOMATION_QUEUE"; 
 AUDIT_ITEM_ID | CLAIMANT | CLAIM_COUNT | CLAIM_TIME | CLIENT_KEY | CREATED | EXECUTION_UUID | ID | PAYLOAD | PRIORITY | RULE_ID | ZIPPED_PAYLOAD 
---------------+----------+-------------+------------+------------+---------+----------------+----+---------+----------+---------+----------------
(0 rows) 

Expected Results

We should be able to mention the priority for the events that should be executed first 

Actual Results

This is hardcoded and priority of the rules can't be adjusted without a manual update from the database(which is not recommended)

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available