Add option to skip workflow failure when JIRA release is already manually marked as "released"

[thomsa-flyr]

Hi,

We are encountering an issue where, if a release has already been manually marked as "released" in JIRA, the action and the entire workflow fail due to a 400 response code from JIRA. Could an option like skip_already_released (or something similar) be added to allow the workflow to continue without failing if the release has already been marked as "released" manually?

Thank you!

[Jira Release Action/jira_release]   💬  ::debug::Project loaded xxxxx
[Jira Release Action/jira_release]   💬  ::debug::Version 1.20.0 found and is going to be updated
[Jira Release Action/jira_release]   💬  ::debug::{"id":"xxxxx","name":"1.20.0","archived":false,"released":true,"startDate":"2024-09-03","releaseDate":"2024-10-01T10:15:58.766Z","userStartDate":"02/Sep/24","projectId":xxxxx}
[Jira Release Action/jira_release]   💬  ::debug::error: Error: Request failed with status code 400
[Jira Release Action/jira_release]   ❗  ::error::Error: Request failed with status code 400
[Jira Release Action/jira_release]   ❌  Failure - Main charpi/[email protected]
[Jira Release Action/jira_release] exitcode '1': failure

After manually testing the API the response is the following:

{
  "errorMessages": [
    "Only one of 'startDate' and 'userStartDate' can be specified when editing a version."
  ],
  "errors": {}
}