Draft: Make JiraConnect SyncMergeRequestWorker idempotent

What does this MR do?

The JiraConnect::SyncMergeRequestWorker sends merge request data to Jira. It does not modify data on GitLab. This means we relay on Jira to handle idempotency and the worker itself is idempotent by default. Declaring it idempotent allows the worker to be retried and might prevent some synchronization failures.

Related issues

• #229174 (closed)
• There is an MR to make the other JiraConnect worker idempotent: !45989 (closed)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• [-] Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• [-] Database guides
• [-] Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team