add ability to pass a different repo-owner and repo-name

[amenocal]

Description:
This PR adds the ability to pass a different repo-owner and repo-name than using the context variable.

This may allow users to specify to run stale on other repositories* (i.e. an Organization Admin marking stale issues / PRs from a centralized repository)

*granted they have the appropriate PAT

Related issue:
#849 It's closed but this has been requested by customers.

Check list:

• Mark if documentation changes are required.
• Mark if tests were added or updated to cover the changes.

[dsame]

Hello @amenocal , thank you for the suggestion, we start to estimate the value of this feature

[amenocal]

@dsame sounds good! I am aware I did this in the most simple approach, but happy to help if there are better methods on approaching this 😄

[andrewwise]

This is exactly what I needed, thanks for this!

[benoittgt]

I would like to know if this PR could be reviewed. There is kind of proposal behind that are interesting, and that use this patch.

[j3tan]

👍 We also have a use case where we have multiple Github organizations with hundreds of repos that we'd like to run this action for. The current approach of adding a workflow to every repo is pretty tedious and hard to maintain if there were any configuration changes. Adding the ability to target a repo allows us to have a single workflow cron that can iterate through all of our organizations and repos (and uses a custom access token) and run the stale action with a set of standardized options.

Please consider merging this change!

[benoittgt]

For you information. I made a feature request for Github also. https://github.com/orgs/community/discussions/85004