Add ignore_missing config

[qiuyin]

📜 Description

config to ignore missing commits previously used in the release

💡 Motivation and Context

add option --ignore-missing to sentry-cli releases set-commits to solve following issue.

There are scenarios in which your repositories may be missing commits previously used in the release. This can happen whenever you modify the commit in question by, for example, amending it, rebasing, or squashing multiple commits together. In this case, Sentry CLI will be unable to find it, and will throw an error that the commit cannot be found.

https://docs.sentry.io/product/cli/releases/#dealing-with-missing-commits

💚 How did you test it?

Before fix, I have this error when deploy

stderr: error: Could not find the SHA of the previous release in the git history. If you limit the clone depth, try to increase it. Otherwise, it means that the commit we are looking for was amended or squashed and cannot be retrieved. Use --ignore-missing flag to skip it and create a new release with the default commits count.

after adding dependency to current pull request branch, the error disappeared

dev_dependencies:
  sentry_dart_plugin:
    git:
      url: https://github.com/qiuyin/sentry-dart-plugin.git
      ref: add-ignore-missing-option

📝 Checklist

• I reviewed submitted code
• I added tests to verify changes
• I updated the docs if needed
• All tests passing
• No breaking changes

Test passed

🔮 Next steps

[marandaneto]

Thank you @qiuyin

[qiuyin]

@marandaneto
Thanks for your review.
I push other commit to fix CHANGELOG.md after your approved.

And integration-test (macos) has failed. It seems like this failure is not related to this PR, Can I ignore it?
https://github.com/getsentry/sentry-dart-plugin/actions/runs/4304457900/jobs/7508506263

[marandaneto]

@marandaneto Thanks for your review. I push other commit to fix CHANGELOG.md after your approved.

And integration-test (macos) has failed. It seems like this failure is not related to this PR, Can I ignore it? getsentry/sentry-dart-plugin/actions/runs/4304457900/jobs/7508506263

yes, likely flakiness.
@vaind the same error as before, tried to rerun but it didn't work.