chore: update stalebot configurations

[mugdha-adhav]

closes #121

What's changed

• Skip adding stale label on any issues/PRs with any milestone.
• Add issue/PR specific days before stale and close values.

Note: These values are not finalized. We would like to try them out for a few months and update them if required.

[mugdha-adhav]

closes #121

[mbtamuli]

@mugdha-adhav If you want the merged PR to close the issue automatically, you have to update the description/first comment. - https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue

[mbtamuli]

I know it isn't related, but could you also update the dependabot commit message prefix in this PR? Perfectly fine to tackle this separately.

https://github.com/warm-metal/csi-driver-image/blob/1fb572f70c2de16c4258dc720e539ba74198b23e/.github/dependabot.yml#L9

I was thinking of having the prefix be - chore: [skip ci]. That'll set us up for conventional commit messages.

It should turn this commit's message
from Bump helm/kind-action from 1.4.0 to 1.8.0
to chore: [skip ci] Bump helm/kind-action from 1.4.0 to 1.8.0

[mugdha-adhav]

but could you also update the dependabot commit message prefix in this PR?

Yes, I have updated it.

[mbtamuli]

@mugdha-adhav If you want the merged PR to close the issue automatically, you have to update the description/first comment. - https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue

FYI, since you haven't linked the issue with the PR correctly, the PR https://github.com/warm-metal/csi-driver-image/issues/121 doesn't show the PR in the development section of the issue. A maintainer will have to do the double work of merging the PR as well as closing the issue.