Issue Summary

When hitting an automation service limit for components used (Max 65) the user is not alerted of this until they attempt to enable the rule:

• Automation Service Limits: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

  Steps to Reproduce

1. Create an automation rule with 66 or more actions, branches, conditions...
2. Attempt to enable the rule and you'll see an error "Rules cannot contain more than 65 components. Delete some components to turn on your rule"

Expected Results

• The rule creator/editor should alert the user that they have hit the max before attempting to save and enable the rule. This would allow them to know the limit was hit and adjust/reconfigure the rule prior to attempting to save/enable.
• This would help prevent users from creating 65+ component rules and then need to backtrack and reconfigure from the point they tried to enable the rule. 

EXAMPLE: 

• If a customer was alerted "You have added 66 components - please remove some to save your rule" while they were configuring, they would likely stop there and work to reconfigure the rule.
• Without this, customers may create rules with 70, 80, or even 90+ conditions and then be forced to review their configuration ONLY when they've attempted to turn on the rule.

Actual Results

This is only seen when trying to enable the rule:

Workaround

Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available