Implementing a Thor task which audits GitHub repositories for stale issues

[jrgriffiniii]

This is a proposed initial step for starting the auditing process identified during the Samvera Northeast Regional Meeting in Princeton, NJ on October 14 - 15, 2024

[jrgriffiniii]

Please note that I have tested this task against the following repositories:

• https://github.com/samvera-deprecated/browse-everything-redux-react
• https://github.com/samvera-deprecated/browse-everything-components

[jrgriffiniii]

I now have this updated to address the following:

• Auditing a repository for stale issues
  • Where issues were created and updated prior to a certain date, the label stale is applied to the issue, the issue is unassigned from any assignees, the issue is removed from any milestones, and a comment is made tagging the creator of the issue notifying them that the issue is now considered stale
• Auditing a repository for CircleCI configuration files
  • If there is no .circleci/config.yml file, if the file does not reference the latest minor release of https://github.com/samvera/samvera-circleci-orb, if the tests do not check for a master branch, or if deprecated releases of ruby or rails are used in testing, then GitHub issues are created indicating these audit failures
• Adding GitHub users to a team within a GitHub organization
• Removing GitHub users to a team within a GitHub organization

[jrgriffiniii]

This now also features Thor tasks for adding and removing owners of a given Gem on RubyGems.