[PROPOSAL] Make Stale Bot settings more aggressive

[MilanKovacic]

Summary:
Repository currently faces a significant backlog of open issues and pull requests, with nearly 1000 open issues and over one hundred open pull requests. Unfortunately, many important issues are going unnoticed due to the current configuration of the stale bot settings.

Proposal:
I propose adjusting the stale bot settings to be more aggressive in identifying and closing stale issues and pull requests. Specifically, I suggest the following adjustments:

Decrease the days-before-stale parameter to a more aggressive setting for all issue and pull request categories. (60 days is default, for example).
Reduce the days-before-close for all issue and pull request categories. (7 days is default, for example).

Benefits:
Promptly addresses stale issues and pull requests, reducing clutter in the repository.
Ensures that important tasks receive attention in a timely manner.
Improves overall repository management and responsiveness.

Analysis of open issues (with type bug), and their lifecycle (semicircles):

[jaysoo]

We'll keep this under consideration. Our goal for May and June is to burn down as many high-priority issues as we can, and then see if additional adjustments need to be made to ensure issues are addressed in a timely fashion.

[MilanKovacic]

Would it be possible to reconsider the proposal?