Don't check subscribers' max-time when verifying the max-tx-rate in tests

[Tempate]

In the previous version, the manual topics's tests configured participants with different max-tx-rates and then verified that the subscribers didn't take less than --min-time (ensuring that the publication frequency got capped) or more than --max-time. At times, however, the publisher would take too long to match the DDS Router and the --max-time would be missed. Ideally, we would measure the time when the subscriber received the first message, but since the subscriber runs in a subprocess and its output is only processed when the subscriber exits, we can't. Therefore, to fix the error, we will bypass the verification of --max-time as it is irrelevant when only configuring the max-tx-rate.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (3ec8299) 31.45% compared to head (90182e7) 31.45%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #419   +/-   ##
=======================================
  Coverage   31.45%   31.45%           
=======================================
  Files          15       15           
  Lines         531      531           
  Branches      274      274           
=======================================
  Hits          167      167           
  Misses        191      191           
  Partials      173      173           

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