Fix default lock kwargs in RedisEventIsolation

[WhiteMemory99]

Description

After the event isolation was rewritten, default Redis lock kwargs, specifically timeout, were left out, causing locks to be permanent, which might result in some users being continuously ignored in case the bot is restarted during the update processing.

Type of change

• Bug fix (non-breaking change that fixes an issue)

How has this been tested?

Test Configuration

• Operating system: Windows 11
• Python version: 3.10.6

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have added tests that prove my fix is effective or that my feature works as expected
• New and existing unit tests pass locally with my changes
• My changes generate no new warnings or errors
• My changes are compatible with minimum requirements of the project
• I have made corresponding changes to the documentation

[github-actions]

✔️ Changelog found.

Thank you for adding a description of the changes

[codecov]

Codecov Report

Merging #972 (611db5a) into dev-3.x (851f7a2) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##           dev-3.x      #972   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          303       303           
  Lines         8179      8178    -1     
=========================================
- Hits          8179      8178    -1     

Flag	Coverage Δ
unittests	100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
aiogram/dispatcher/fsm/storage/redis.py	100.00% <100.00%> (ø)