[O2B-719] Add range based filtering for run number

[hattinf]

I have a JIRA ticket

• branch and/or PR name(s) include(s) JIRA ID
• issue has "Fix version" assigned
• issue "Status" is set to "In review"
• PR labels are selected

Notable changes for users:

• runNumber filter now accepts ranges as well

Notable changes for developers:

• N/A

Changes made to the database:

• N/A

[codecov]

Codecov Report

Attention: Patch coverage is 96.96970% with 1 line in your changes missing coverage. Please review.

Project coverage is 44.10%. Comparing base (ccb2bbb) to head (2500ad5).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
lib/domain/dtos/filters/RunFilterDto.js	91.66%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1810      +/-   ##
==========================================
+ Coverage   44.02%   44.10%   +0.07%     
==========================================
  Files         891      891              
  Lines       15898    15922      +24     
  Branches     2999     3006       +7     
==========================================
+ Hits         6999     7022      +23     
- Misses       8899     8900       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[martinboulais]

The idea is good, but there is a major flaw: when using a very big range (with prod data) the app simply crash because the list of run numbers is too big.
A possible solution is to limit the range, for example to 100 (please read Joi documentation to put it in the DTO).
The best solution would be to use min and max SQL function for run, but I am not sure we can properly do that with the current query builder.