fix: hide sensitive data from debug logs

[kinueng]

Fixes #1796

With my limited knowledge of this code base, I have tried to patch the specific scenario reported in #1796.

I think there can be improvements to this code but I lack the code base knowledge to put this logic in an universal place where all logs will sanitize values associated with the command auth.

How I tested using [email protected]

1. docker pull redis/redis-stack-server:latest
2. docker run -d --name redis-stack-server -p 6379:6379 redis/redis-stack-server:latest
3. npm install ioredis
4. Edit node_modules/ioredis/built/utils/debug.js directly with this PR code
5. Run DEBUG=ioredis:* node app.js with the file below.

const http = require('http');
const Redis = require('ioredis');

const hostname = '127.0.0.1';
const port = 3000;

const redisClient = new Redis({
    host: 'localhost',
    port: 6379,
    password: 'foobar'
});

redisClient.on('connect', () => {
    console.info('connected to redis server');
});

const server = http.createServer((req, res) => {
  res.statusCode = 200;
  res.setHeader('Content-Type', 'text/plain');
  res.end('Hello World');
});

server.listen(port, hostname, () => {
  console.log(`Server running at http://${hostname}:${port}/`);
});

5. Observed the log and see message ioredis:redis write command[127.0.0.1:6379]: 0 -> auth('***********') +1ms

[HardikJade]

Suggestion