chore: exempt stale if milestone is set

[qweeah]

This PR adds a workflow change which will avoid marking PRs or issues as stale if any milestone is tagged.

[codecov-commenter]

Codecov Report

Merging #1036 (393a62c) into main (0b6651a) will not change coverage.
The diff coverage is n/a.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@           Coverage Diff           @@
##             main    #1036   +/-   ##
=======================================
  Coverage   81.25%   81.25%           
=======================================
  Files          57       57           
  Lines        2912     2912           
=======================================
  Hits         2366     2366           
  Misses        373      373           
  Partials      173      173           

[TerryHowe]

/lgtm

[sajayantony]

Thanks for the change @qweeah - This also means we should review the milestones regularly so that issues don't get stale in there. Honestly I'm happy that a lot of old issues got bumped and makes the maintainers consider if we actually will ever get to it.

Future seems like a backlog milestone, should we avoid moving everything to future unless there is plan and/or close them off since there is no immediate plan would be a question for us to agree on.