GEODE-8931: Support Redis GETRANGE command

[jdeppe-pivotal]

Thank you for submitting a contribution to Apache Geode.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

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?

Note:

Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to dev@geode.apache.org.

[nonbinaryprogrammer]

looks good but can you add a test for the right number of command line options?

[jdeppe-pivotal]

looks good but can you add a test for the right number of command line options?

I think these are the tests you are looking for:

geode/geode-redis/src/integrationTest/java/org/apache/geode/redis/internal/executor/string/AbstractGetRangeIntegrationTest.java

Lines 53 to 76 in 1018ece

	@Test
	public void givenKeyNotProvided_returnsWrongNumberOfArgumentsError() {
	assertThatThrownBy(() -> jedis.sendCommand(Protocol.Command.GETRANGE))
	.hasMessageContaining("ERR wrong number of arguments for 'getrange' command");
	}
	@Test
	public void givenStartNotProvided_returnsWrongNumberOfArgumentsError() {
	assertThatThrownBy(() -> jedis.sendCommand(Protocol.Command.GETRANGE, "key"))
	.hasMessageContaining("ERR wrong number of arguments for 'getrange' command");
	}
	@Test
	public void givenEndNotProvided_returnsWrongNumberOfArgumentsError() {
	assertThatThrownBy(() -> jedis.sendCommand(Protocol.Command.GETRANGE, "key", "1"))
	.hasMessageContaining("ERR wrong number of arguments for 'getrange' command");
	}
	@Test
	public void givenMoreThanFourArgumentsProvided_returnsWrongNumberOfArgumentsError() {
	assertThatThrownBy(
	() -> jedis.sendCommand(Protocol.Command.GETRANGE, "key", "1", "5", "extraArg"))
	.hasMessageContaining("ERR wrong number of arguments for 'getrange' command");
	}

[sabbey37]

I was just thinking, we don't have a test verifying the error message when the start/end integers are more than the min/max value. The min in Redis is -9,223,372,036,854,775,808 and max is 9,223,372,036,854,775,807