feat: Add ability to manually submit release repo/commits

[trevorkwhite]

This PR adds support for a "manual" commit range that is already supported by the CLI, but not by the action.

Since we squash and merge and have a unique setup, it's necessary to manually specify commits. This PR allows that by adding a commit_range option in addition to a manual enum on the set-commits option.

While it isn't perfect, I used a comma separated list to capture repo, current commit, previous commit. Open to doing this a cleaner way, but I didn't want to add 3 options. Perhaps it would be better to explicitly tag each of these.

PR is early, wanted to see whether this was something ya'll were open to adding.

[andreiborza]

Hi @trevorkwhite, thank you for contributing this. I created #287 to track this and proposed an alternative api. We should definitely support this!

[andreiborza]

I think instead of manual we could just supply a commit or a commit-range in the same format as sentry cli has it documented: https://docs.sentry.io/cli/releases/#commit-integration

No need to parse/split it and no need for extra args.

What do you think about that?

[trevorkwhite]

Absolutely. I'll go ahead and make those changes to update this PR

[trevorkwhite]

@andreiborza took a stab at updating the api per our conversation. I'm not super-duper familiar with node, so if the map is a crappy option, I won't take offense. Take a peek, let me know what you think, can go from there. Used regex to match the repo/commit syntax (including previous commit)