Fix timing issue in EXEC fail on lazy expired WATCHed key test (#10332)
Fix timing issue in EXEC fail on lazy expired WATCHed key test (#10332)

The test will fail on slow machines (valgrind or FreeBsd).
Because in #10256 when WATCH is called on a key that's already
logically expired, we will add an `expired` flag, and we will
skip it in `isWatchedKeyExpired` check.

Apparently we need to increase the expiration time so that
the key can not expire logically then the WATCH is called.
Also added retries to make sure it doesn't fail. I suppose
100ms is enough in valgrind, tested locally, no need to retry.
neomantra/redis,charsyam/redis,PKRoma/redis,charsyam/redis,yossigo/redis,ofirluzon/redis,oranagra/redis,oranagra/redis,PKRoma/redis,yossigo/redis,oranagra/redis,antirez/redis,ofirluzon/redis,antirez/redis,soloestoy/redis,yossigo/redis,neomantra/redis,ofirluzon/redis,ofirluzon/redis,neomantra/redis,soloestoy/redis,soloestoy/redis,charsyam/redis,ofirluzon/redis,PKRoma/redis,PKRoma/redis,PKRoma/redis,neomantra/redis,antirez/redis,oranagra/redis,soloestoy/redis,antirez/redis,charsyam/redis,oranagra/redis,yossigo/redis,neomantra/redis,soloestoy/redis,yossigo/redis,charsyam/redis