[Spike] Investigate why older issues are not following issue lifecycle

[michael-valdron]

Which area/kind this issue is related to?

/kind task

/area ci

Issue Description

A large portion of our older issues are not following the issue lifecycle via the automation, i.e. label lifecycle/stale after 90 days then label lifecycle/rotten and close after an additional 60 days under lifecycle/stale.

An investigation should be conducted to find out how to resolve this to prune our backlog. Found solution should still not effect issues labelled lifecycle/frozen as this is intentional.

Acceptance Criteria

• Find solution to correct the automation into including issues older than the automation was implemented

[Jdubrick]

Was reading through the logs for our stale workflow here https://github.com/devfile/api/actions/runs/9200010231/job/25305811607 and noticed it is only processing 90 issues and has a warning about operations-per-run. Since I think the workflow is an authenticated user the rate limit shouldn't affect it and we may be able to try and jack this value up to cover all 300 something open issues.