Hash keys locally rather than call cluster keyslot

[upthewaterspout]

Changing the remaining commands in JedisClusterKeyCommands to use the
topology's getKeyServingMasterNode to find the node of key, rather than calling
connection.clusterGetNodeForKey. clusterGetNodeForKey was making a cluster
keyslot call to the server to hash the key, rather than hashing it locally.

Closes: #2156

• You have read the Spring Data contribution guidelines.
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.
• You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

[mp911de]

I think it's easier to switch clusterGetNodeForKey to calculate the slot locally instead of obtaining the TopologyProvider. We have the same behavior already in place for Lettuce, so it makes sense to align the Jedis implementation.

Thank you for your contribution. That's merged, polished, and backported now.