Use streaming instead of RBNO for a few longevity tests

[pehala]

Overview

• Use streaming for one tier1 (longevity-mv-si-4days) and one tier2 (longevity-cdc-8h-multi-dc-topology-changes) longevity tests

Testing

• Run longevity-mv-si-4days in jenkins
• Run longevity-cdc-8h-multi-dc-topology-changes in jenkins

PR pre-checks (self review)

• I added the relevant backport labels
• I didn't leave commented-out/debugging code

Questions

• Are those two tests enough? Should I add more tests from different categories?
  • Are those even right tests?
• How can I verify that it uses streaming?
• For how long do I need to run tests to verify correctness of this PR?

Fixes #8289

[roydahan]

I'm not in favor of the renaming, it helps to have the history in one place.
If we do that renaming to make it clear that this one uses streaming, maybe it would be better to duplicate these and just replace the ones we have in in tier1 with them.
(i.e. move the originals to "longevity" and put the new ones in tier1, tier2).

[fruch]

I'm not in favor of the renaming, it helps to have the history in one place. If we do that renaming to make it clear that this one uses streaming, maybe it would be better to duplicate these and just replace the ones we have in in tier1 with them. (i.e. move the originals to "longevity" and put the new ones in tier1, tier2).

also we should add the new jobs into the tier1/teir2 triggers while we add them

[pehala]

• Move old tests to longevity
• Change triggers to use new tests

[roydahan]

LGTM

[fruch]

LGTM

[fruch]

@pehala

A general comment, if you run any Jenkins jobs, please supply link to them or to Argus, so whom need would be able to cross check what was running

[fruch]

@roydahan @pehala

Do we want to change the triggers for release 2024.1 as well ?

[roydahan]

Preferably yes, assuming we tested them.