feat(options): add new options to avoid stale based on comments

[C0ZEN]

Changes

• Add 3 new options to avoid staling when a comment is added
• The scope of remove-stale-when-updated will be reduced, resulting in a breaking change (@luketomlinson for the release notes!) when using the option at false

⚠️ this is a breaking change

Context

Helping to close (maybe) #441, #470, #435?
Closes #390 due to no activity

[C0ZEN]

I'm kind of stuck with the issue it caused.
May need help...

[jeremystretch]

@C0ZEN what's the issue?

[C0ZEN]

It makes sense to have this feature but the current implementation is actually helping the case where an issue is marked as stale then still in the same workflow process it for closing process. In such case the freshly staled issue update date is set as today and with the current implementation provided in this PR it will consider the issue as no longer stale if a comment was added. If the new option to install when commented is disabled there is no problem

[C0ZEN]

The last added test is actually failing because just after staling, the workflow continue and then consider the issue as stale but to unstale due to shouldRemoveStaleWhenUpdated && issueHasUpdate being both true.

[C0ZEN]

I close it because I just don't understand the whole workflow.
Each time I change something a test is failing, and actually, I can't define if its bad tests or a bad changes.
The fact that the specs are mocking the label creation date and all the logic to calculate if either or not it should stale or close seems terrible IMO.
What could be nice is to rewrite this whole part — code and specs included — and I just don't have the courage to do so.
Well, free to continue the work from this branch or just tackle this from scratch.