use redis 3 for tls

[b-jam]

As previously discussed in #257
In the interest of security, to utilisize rediss over TLS. I noticed dependabot was also complaining about redis too.

It seemed like no progress is being made towards bee-queue 2.0 or using IOredis so this is necessary.

Node 4 support needs to be dropped as a result, but that was EOL in 2018
(Node 8 is also EOL as is 10) https://endoflife.software/programming-languages/server-side-scripting/nodejs

[chrislim]

Is there any hope of this PR being accepted?

[kourylape]

LGTM 👍

[compwright]

@chrislim @b-jam I'm accepting this PR over here: compwright#5

[bradvogel]

Thanks @compwright . This project is looking for a new maintainer if you're interested: #528

[compwright]

@bradvogel this is ready to go, priority

[compwright]

@bradvogel CI checks seem to be stuck, and it won't let me merge until those pass. We will need to drop support for Node 4-10, since dependencies used in this project no longer support those versions. I seem to be missing some project permissions to resolve this, can you help?

[bradvogel]

@compwright I just upgraded you to the "Maintain" role. Are you able to fix now?

[compwright]

@bradvogel no. I either need a way to re-run the checks on this branch (I may be missing something here), or to override the merge restriction.

[bradvogel]

@compwright Here's what I see as an admin. It looks like CI is stuck? I have no way to re-run it either.

What level of access do you need to fix CI?

[compwright]

@bradvogel I would need repo admin to manage branch protection rules. I don't have the override checkbox you see there. https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/repository-roles-for-an-organization

[compwright]

Resubmitted to re-trigger CI checks #546