Issue Summary

When Atlassian Studio AI (studio-sa-create) generates an automation rule containing "Edit work item" actions with date fields, it stores field references using the field display name as the value where the automation engine expects an actual field ID (e.g., customfield_10600, duedate). This causes the automation rule editor to show those fields as deleted/missing every time the rule is opened.

Steps to Reproduce

1. Use Atlassian Studio AI to create an automation rule that includes an Edit work item action referencing date fields such as Start date, Due date, or any custom date field (e.g., Go Live Date).
2. Open the generated rule in the automation rule editor.
3. Observe that the date fields in the Edit work item action are flagged as deleted fields.

Expected Results

Studio AI should resolve the actual field ID from the Jira API (GET /rest/api/2/field) at rule generation time and store the correct field ID (e.g., customfield_10600) in the rule JSON when type='ID' is used.

Actual Results

All automation rules generated by Studio AI that reference Jira fields in Edit work item actions are potentially affected.
The rule may execute incorrectly or skip field updates entirely at runtime since the field reference cannot be resolved.
Users see confusing "deleted field" warnings on rules that were just created by AI and never manually edited.

Workaround

The customer must manually re-select each affected field from the field picker in the rule editor and save the rule. The picker selection stores the correct field ID.