Currently, the ci-signal handbook instructs the ci-signal team to drop outdated test-infra logic and unsupported versions during Step 3 and 4 of "Setup jobs and dashboards for a new release branch."

However, during the v1.10 release cycle, it was decided to retain support for v1.7 even after creating jobs and dashboards for v1.10. The plan is to drop support for v1.7 after the end of the release cycle, not during the setup phase.

I'm opening this issue to get consensus on where in the process this step should happen and ensure we capture the correct task and timing in the handbook. Once we align, we can update the handbook accordingly.

/area release
/kind cleanup