Add schedule for staling issues

[sunjayBhatia]

To whittle down issues a little, to ensure we're focusing on things that are deemed important and are getting proper community attention.

Stale after 60 days, closed after another 30

Exempted a few labels from being staled as well.

[codecov]

Codecov Report

Merging #4752 (91e3fce) into main (6bde6ff) will decrease coverage by 0.00%.
The diff coverage is n/a.

❗ Current head 91e3fce differs from pull request most recent head bc9189e. Consider uploading reports for the commit bc9189e to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4752      +/-   ##
==========================================
- Coverage   75.67%   75.66%   -0.01%     
==========================================
  Files         140      140              
  Lines       16836    16836              
==========================================
- Hits        12740    12739       -1     
- Misses       3842     3843       +1     
  Partials      254      254              

Impacted Files	Coverage Δ
internal/sorter/sorter.go	97.32% <0.00%> (-0.54%)	⬇️

[sunjayBhatia]

modified the project board to move existing priority/important-soon items to priority/important-longterm, planned things on the project board now have priority/important-soon

[skriss]

LGTM, thanks for updating the messages.

I'm in favor of doing this, along with better triage of issues as they're opened, to better manage our backlog and reflect to our users what our priorities are. Having a smaller/more focused backlog will be more useful for both maintainers and users, while not preventing anyone from "helping themselves" if they have a specific issue they want to contribute on.