Allow filtering by job id

[iamnafets]

Some workflows you may want to filter by the last workflow with a specifically-named successful job. This PR adds an additional parameter to do this.

[domi2120]

@iamnafets I've reviewed the changes and noticed the change to the behaviour if no matching run has been found. Previously the current SHA was returned, but with this PR the earliest SHA will be returned instead. Is there a specific reason for this change?

[VeoVirt]

+1 for this PR to be approved, you should not use the triggeringSHA if you cannot find a successful run. A good use-case for this action is that you can use it for checking if a scheduled build can be skipped when the sha has been built before. It currently breaks on the first build of a workflow or if all builds in a workflow has failed, then the github.sha and last-succesful-build.outputs.sha will always be equal. Also the name "last-successful-build" is misleading since it can return the triggering sha even though it does not correspond to a succesful build.

[gabbersepp]

I will merge the PR but add another option to control what should be done when no build was found. I was not able to determine of the changed behaviour will break no existing behaviour in our builds.