ci: stale bot is far to agressive

[Neudrino]

Summary

Stale bot was introduced without TSC vote or any community announcement with #11933. Amongst the over 1250 closed issues were a lot of very valid and elaborate issues and proposals.

There are several issues with the current implementation which are addressed with this PR:

• Configuration from the Bot was copied but no license header was given.
• The wait time for the bot
  • was reduced below the default without reasoning.
  • is far too short and would even close issue from active developers just going for a vacation.
• The exempt label list is incorrect and needs to be extended to work well with other automation.
  • The label should be called willfix and not status: willfix due to following reasons:
    • Inconsistency between wontfix and status: willfix vs. willfix label.
    • The label status: willfix was not created for the repository and is nowhere used.
    • The label willfix was created and is currently used 44 times.
  • Additional labels should be added, amongst others proposals, ready-to-merge PRs and issues created by the Sentry automation should likely never be closed automatically.
• The comment text is misleading as
  • it only refers to PRs and not issues, while both are affected.
  • suggests that only authors and maintainers can take action while anybody can.

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[maxhbr]

LGTM

[maxhbr]

The only blocking CI check is checkRebase, I think it still can be reviewed.

[maxhbr]

still LGTM