Automation support for working with components and component leads - new triggers, actions and smart values

Suggested improvements

• Right now only component names can be accessed with Jira Automations. A sample Use Case would be to create sub-tasks for every component added to an issue and assigning their component lead to those. Accessing to the component lead could be possible like this: { {issue.fields.component.lead.displayName}

  . Right now this is not possible without an API call which is taking way longer and is much more complicated and much more prone to error.

• Include project components create/edit actions as a trigger - Support to configure rule triggers based on project component create/edit actions so automation rules can be used to configure action upon that activity.