Allow release on a commit that is not the latest

Hi,

First thanks for the action, we find it quite useful!

We ran into a limitation the last time we released because we selected a commit that wasn't the latest commit, it happens sometimes that we don't want to release the newest commits because they rely on another service that is not deployed yet.

The action fail with these logs
```
[7:57:25 AM] [semantic-release] › ✔ Loaded plugin "success" from "@semantic-release/github"
[7:57:25 AM] [semantic-release] › ✔ Loaded plugin "fail" from "@semantic-release/github"
[7:57:28 AM] [semantic-release] › ✔ Run automated release from branch main on repository https://github.com/AgicapTech/cm-cashflow-reconciliation-app
[7:57:29 AM] [semantic-release] › ℹ The local branch main is behind the remote one, therefore a new version won't be published.
```

I looked into the config options but did not find anything to allow tagging a commit that is not the latest, did I miss an option and if not would you consider allowing that use case ?

Thanks

Start by tracing the semantic-release run described in the issue and the check that reports the local branch is behind the remote one. Done means the action can publish a selected non-latest commit without rejecting the release; no source files or tests are named in the report.

Written by the indexing model from the issue text.