[COREDEV] introduce a PR test-process

          Next time we should ad some zombienet test for syncing to ensure we don't break it again :D

Originally posted by @bkchr in #13409 (review)

Process should be mandatory

(example)

core developers

Mandatory "zombienet" Test

• if your change affects xyz
  • use zombienet-n for testing (pre Merge)
    • via cli 'docker ...'

Mandatory Regression Test

• if you revert a merge (commit, PR), either
  • provide a new automated regression test that catches the error
    • or (in the case an automation is not possible or high effort)
      • provide a manual regression test step in the Core Developer Manual

[bkchr]

We have a test process and always extending our tests. You will not find that much prs that go in without any new tests.

[bkchr]

but mostly about a process that ensures that test-processes are always extended when an new incident occurs.

As I said, this is already things we are doing. We have added dozens of tests to ensure that incidents are not gonna happen again.

[bkchr]

Then please inform me, what is the essence? Maybe I'm missing it. Sorry