fix: added newFilter to paramRearrangementMap for WS server

[quiet-node]

Description:
There's a regression in the WS server that breaks the eth_newFilter WS endpoint. Essentially, before the data is submitted to the Relay, there’s a step to rearrange the parameters for certain special endpoints that have a different parameter order than others. This step is handled by the paramRearrangementMap, but it missed the newFilter endpoint, so the parameters weren't ordered correctly, causing the eth_newFilter endpoint to fail.

This PR simply adds the newFilter method to the paramRearrangementMap, fixing the issue.

Related issue(s):

Fixes #3114

Notes for reviewer:

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[github-actions]

🚨 Memory Leak Detected 🚨

A potential memory leak has been detected in the test titled validates enforcement of request id. This may impact the application's performance and stability.

Details

📊 Memory Leak Detection Report 📊

GC Type: MarkSweepCompact
Cost: 30,509.8 ms

Heap Statistics (before vs after executing the test):

• Total Heap Size: increased with 1.46 MB
• Total Heap Size Executable: no changes
• Total Physical Size: decreased with 348.16 KB
• Total Available Size: decreased with 9.33 MB
• Total Global Handles Size: no changes
• Used Global Handles Size: decreased with 64.00 bytes
• Used Heap Size: decreased with 3.45 MB
• Heap Size Limit: no changes
• Malloced Memory: no changes
• External Memory: no changes
• Peak Malloced Memory: no changes

Heap Space Statistics (before vs after executing the test):

• Old Space:

  • Space Size: increased with 1.84 MB
  • Space Used Size: increased with 2.07 MB
  • Space Available Size: decreased with 12.90 MB
  • Physical Space Size: increased with 1.84 MB

• Large Object Space:

  • Space Size: increased with 835.58 KB
  • Space Used Size: increased with 813.50 KB
  • Space Available Size: no changes
  • Physical Space Size: increased with 835.58 KB

Recommendations

Please investigate the memory allocations in this test, focusing on objects that are not being properly deallocated.

[github-actions]

Tests

       3 files     399 suites   18s ⏱️
1 433 tests 1 432 ✔️ 1 💤 0 ❌
1 442 runs  1 441 ✔️ 1 💤 0 ❌

Results for commit 2bd1602.

♻️ This comment has been updated with latest results.

[Nana-EC]

Looks good but needs tests

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Acceptance Tests

  19 files  290 suites   30m 6s ⏱️
599 tests 591 ✔️ 4 💤 4 ❌
879 runs  869 ✔️ 4 💤 6 ❌

Results for commit 2bd1602.

[ebadiere]

LG.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.46%. Comparing base (9e73aae) to head (2bd1602).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3117      +/-   ##
==========================================
- Coverage   85.53%   83.46%   -2.08%     
==========================================
  Files          45       66      +21     
  Lines        3387     4402    +1015     
  Branches      673      868     +195     
==========================================
+ Hits         2897     3674     +777     
- Misses        282      459     +177     
- Partials      208      269      +61     

Flag	Coverage Δ
relay	85.59% <ø> (+0.05%)	⬆️
server	83.48% <ø> (?)
ws-server	36.15% <100.00%> (?)

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

Files with missing lines	Coverage Δ
packages/ws-server/src/utils/utils.ts	98.07% <100.00%> (ø)

... and 28 files with indirect coverage changes