Pin redis!=4.5.2 and redis!=4.5.3
Turns out the bug we found and described in #556 (closed) was identified by by the redis team and fixed in 4.5.4 by this PR. This means the bug also exists in 4.5.3, so this MR just requires redis not be 4.5.2 or 4.5.3.