GEODE-9740: require DATA:WRITE permission for WRITE redis ops and PUBLISH

[dschneider-pivotal]

Redis commands with the WRITE flag and the PUBLISH command will require DATA:WRITE.
All other commands will require DATA:READ.

Options

For all changes:

• Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

• Has your PR been rebased against the latest commit within the target branch (typically develop)?

• Is your initial contribution a single, squashed commit?

• Does gradlew build run cleanly?

• Have you written or updated unit tests to verify your changes?

• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[jdeppe-pivotal]

Looks good. Could you also add an integration test (maybe to AuthIntegrationTest) that exercises this with read and write commands.

[upthewaterspout]

Looks pretty good!

Looking through the flags in RedisCommandType, I think a few commands might need to be updated? Some commands are marked neither READONLY nor WRITE, so they default to requiring write permission in our scheme. But maybe that's not the right thing?

• PING
• ECHO
• COMMAND
• INFO
• LOLWUT
• SUBSCRIBE, PSUBSCRIBE, UNSUBSCRIBE, ??
• PUBSUB
• CLUSTER

That last one - cluster, means I think that a readonly client currently couldn't really work. This might have only worked because the AuthIntegrationTest is not using a clustered client. I think it probably should.

[nonbinaryprogrammer]

looks good but I'd like a couple more tests