Workflow improvements

[DanyHenriquez]

Reason for the change

• A lot of PR's and issues are open without any action. These should be closed automatically when stale
• Dependency updates also bring security fixes. This should be taken seriously. Therefore we should use a reliable mechanism for auto updates (Renovate)

Description
See reasons

Code examples
Not applicable

Checklist

• I have read and agreed to the RethinkDB Contributor License Agreement

References
Anything else related to the change e.g. documentations, RFCs, etc.

[gabor-boros]

@DanyHenriquez Although I agree with the intention, the repository is not that active to automatically close the issues or PRs. How about cleaning up the issues and if still needed, we can merge this later?

[DanyHenriquez]

@DanyHenriquez Although I agree with the intention, the repository is not that active to automatically close the issues or PRs. How about cleaning up the issues and if still needed, we can merge this later?

On second thought we should only tag PR's as stale anyway in stead of closing things without a human verifying the closure.

Of course we can do this later