Add static routes to netConfig to support scenario A

[averdagu]

Adopting a workload using scenario A (different subnet ranges between wallaby CP and next-gen CP) wont succeed if netConfig doesn't have the routes to reach old CP.

Relates: OSPRH-7544

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign archana203 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@averdagu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/unit	24b9574	link	true	/test unit

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/96f987176e814792beedcd98d60c7eb5

✔️ noop SUCCESS in 0s
✔️ adoption-standalone-to-crc-ceph SUCCESS in 3h 01m 15s
❌ adoption-standalone-to-crc-no-ceph RETRY_LIMIT in 48m 15s

[averdagu]

recheck

[softwarefactory-project-zuul]

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/7642f2ffde2146fbafd30cc22d1231a0

✔️ noop SUCCESS in 0s
✔️ adoption-standalone-to-crc-ceph SUCCESS in 3h 02m 42s
❌ adoption-standalone-to-crc-no-ceph RETRY_LIMIT in 14m 15s

[karelyatin]

why we need to change defaults? should we apply this only for the envs where we need to modify it?

[averdagu]

I thought that this won't affect on the default scenario, as this route is already added by system (since the interface belongs already to 172.17.0.0/24) and I didn't want to overengineer it). But I could modify it to only modify it in case it's the scenario A (though this may need some extra variable from install_yamls)