Add the Stale Action to select GitHub repos used by our team(s)

[WadeBarnes]

Add a scheduled workflow using the Stale Action to select repositories to automate the management of long lived Issues and PRs.

The intent is to automate the management of issues and PRs we're unable to address in a timely fashion. The actions taken by the automation will provide us with reminders that no actions have been taken on an item in a given amount of time and then automatically close (clean-up) the items if no actions are taken of another amount of time.

We have been using this action on the bcgov/traction and bcgov/vc-authn-oidc repositories for a while now, though the settings could use some optimization.

Approach:

1. Determine which repositories should be considered in scope for this task. Repositories from the bcgov, hyperledger, and openwallet-foundation should be considered. Discuss with the DITP team members and the community working on the code within these various organizations to compile a list of candidate repositories.
2. Determine the best settings and schedule(s) to use for the action. Discuss with the DITP team and the community who are actively addressing issues and PRs to determine what time spans are most appropriate for the stale and close settings, the most appropriate messages to post along with each step, which labels that should exempt an item from becoming stale, along with any other settings appropriate for all or select repositories. There are lots of setting to consider.
3. Draft PRs for each selected repository, complete with common and customized settings.

Acceptance Criteria:

1. Acceptance criteria may vary depending on the repository and the community maintaining it. Acceptance will ultimately be decided by maintainer review and approval of the submitted PR. However, in general is expected to be based on a complete, functional, and easily maintainable Stale Action workflow that has settings appropriately configured for the given repository.

Bonus Points:
For bonus points, the PR submission should also include a new or updated dependabot.yml configuration to ensure the GitHub action dependencies are updated on a regular bases using a configuration like this.

[WadeBarnes]

Queries representing the candidate repositories for this task can be found here; #175 (comment)

[WadeBarnes]

Queries representing the candidate repositories for this task can be found here; #175 (comment)

Top 5 Candidates:

• bcgov/vc-authn-oidc
• bcgov/bc-wallet-mobile
• bcgov/BC-Wallet-Demo
• bcgov/traction
• bcgov/indy-tails-server
• hyperledger/aries-cloudagent-python
• hyperledger/aries-agent-test-harness
• openwallet-foundation/bifold-wallet

Edit: - List has been updated, bcgov/von-network was replaced with bcgov/vc-authn-oidc in the top 5 list, as bcgov/von-network's dependabot.yml file has already been configured. bcgov/von-network still needs to be updated with Stale Action.

Edit: - Updated the list. Added the bcgov/BC-Wallet-Demo repo and removed the openwallet-foundation/bifold-wallet repo for now. This will provide some additional practice on our repos before branching out to more global repos.

Edit: - Updated the list. Limited the top 5 to BC Gov repos. This will provide some additional practice on our repos before branching out to more global repos.