issue #2153 - honor sentinel configuration params within MasterListener

[timmixell]

I could use some assistance/direction on proper unit test coverage, but I confirmed that the change addresses issue 2153 in our environment. Thank you!

Closes #2124
Resolves #2153

[timmixell]

My sincere apologies. I didn't realize that there were already open PRs addressing this issue when I submitted this yesterday. Upon closer inspection, it looks like this PR would handle the scenario more gracefully when the target Sentinel is unavailable (i.e. if j.auth() throws a JedisException). I'm pretty sure this PR should be closed out in favor of #2124.

[sazzad16]

@timmixell Could you please move all the changes including new Jedis object creation after if block of double check?

[gkorland]

This file seems like it needs a full refactor

[gkorland]

And it seems like we're missing a test to test this use case,

[timmixell]

@gkorland , I'll get one in. I wasn't sure if this PR was going to survive, given that there are a couple other PRs addressing this issue.

[timmixell]

@gkorland I'm struggling a bit on the best approach to write a unit test to support this use case. Do you have any suggestions? Thanks!

[sazzad16]

@gkorland Perhaps we can merge it right now and create a new task to write test(s). WDYT?