Reduce rewriteClientCommandVector usage on EXPIRE command

[filipecosta90]

As being discussed in #10981 (comment) there is overhead on 7.0 EXPIRE command that is not present on 6.2.7.

We can see that on the unstable profile there are around 7% of CPU cycles spent on rewriteClientCommandVector that are not present on 6.2.7. This was introduced in #8474.
This PR reduces the overhead by using 2X rewriteClientCommandArgument instead of rewriteClientCommandVector. In this scenario rewriteClientCommandVector creates 4 arguments. the above usage of rewriteClientCommandArgument reduces the overhead in half.
This PR should also improve PEXPIREAT performance by avoiding at all rewriteClientCommandArgument usage.

6.2.7 profile:


unstable profile:

If we populate data as follows:

memtier_benchmark --port 6379 --server localhost   --key-minimum=1 --key-maximum 100000 "--data-size" "100" "--command" "HSET __key__ field __value__" "--command-key-pattern" "P" "-c" "50" "-t" "2" "--hide-histogram"

And then benchmark:

memtier_benchmark  --pipeline 10 --key-minimum=1 --key-maximum 100000 "--data-size" "100" --command "EXPIRE __key__ 3600" --command-key-pattern="R" -c 50 -t 2 --hide-histogram --test-time 180

we get the following results on the achievable ops/sec:

test	Version 6.2.7	unstable branch 8th December 2022 ( 10e4f44 )	% change unstable vs 6.2.7	this PR	% change this PR vs 6.2.7
EXPIRE ( pipeline 10 )	876843	770614	-12.1%	821241	-6.3%

[filipecosta90]

@oranagra after your change I did a new check.
We're with a 5% GAP vs 6.2.7 =)

test	Version 6.2.7	unstable branch 9th December 2022 ( 528bb11 )	% change unstable vs 6.2.7
EXPIRE ( pipeline 10 )	876843	830212	-5.3%