chore: Update Closed Stale Issues Github Action

[jfuss]

Which issue(s) does this change fix?

None

Why is this change necessary?

To reduce the load on maintainers, we will close stale issues. This keeps lingering issues to a minimum and gives maintainers better view of the repo state.

How does it address the issue?

GHA will run daily, and look for stale issues. If a stale issue is found and does not have an exempt label, it will be marked "stale". Once the issue is in a stale state, it will be closed after a determined about of time (see config).

This will not closed except labels, issues with 1 or more reactions, and issues that have been recently commented on.

What side effects does this change have?

This will close issues and mark them stale but should be done only after a maintainer responses first (and removes one of the exempt labels set by default). If there are issues, the issues can always be reopen, making this not something we are locked into and can get around.

Mandatory Checklist

PRs will only be reviewed after checklist is complete

• Add input/output type hints to new functions/methods
• Write design document if needed (Do I need to write a design document?)
• Write/update unit tests
• Write/update integration tests
• Write/update functional tests if needed
• make pr passes
• make update-reproducible-reqs if dependencies were changed
• Write documentation

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.