Static routes aren't deleted after rehoming a subcloud.

[Gustavo Lyra Pereira]

Brief Description
-----------------
Rehoming a subcloud adds the new controller route but
leaves the previous controller route.

Severity
--------
Provide the severity of the defect.

<Minor: System/Feature is usable with minor issue>

Steps to Reproduce
------------------
Create a dc system, remove the controller.
Shutdown the controller.
Create a new controller with different mgmt network configs.
Rehome the subcloud to the new controller.

Expected Behavior
------------------
Previous controller route is removed.

Actual Behavior
----------------
The static routes still existed after the rehome completed successfully.

Reproducibility
---------------
No attempt made to reproduce, but it looks like the ansible scripts don't account for deleting the old static route so I would assume this occurs every time the subcloud is rehomed.

System Configuration
--------------------
DC

Branch/Pull Time/Commit
-----------------------
Branch and the time when code was pulled or git commit or cengn load info

Last Pass
---------
Unknown

Timestamp/Logs
--------------
NA

Test Activity
-------------
NA

Workaround
----------
Remove the route manually.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/ansible-playbooks/+/898675

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/starlingx/ansible-playbooks/+/898675
Committed: https://opendev.org/starlingx/ansible-playbooks/commit/f7dda70a7c3c5a10583e17b060dccce6c4ee0d4d
Submitter: "Zuul (22348)"
Branch: master

commit f7dda70a7c3c5a10583e17b060dccce6c4ee0d4d
Author: Gustavo Pereira <email address hidden>
Date: Tue Oct 17 13:55:57 2023 -0300

    Static routes aren't deleted after rehoming a subcloud

    This commit fixes the issue of not deleting the previous
    routes created on a subcloud after its being rehomed.

    Test Plan:

    PASS: Deploy a dc system with one controller and one
    subcloud. Check the route to the system controller by
    running "system host-route-list controller-0" in the
    created subcloud.
    Shutdown the previously created system controller and
    create a new system controller with different mgmt
    network configuration.
    Rehome the subcloud to the new controller and check
    that the route has changed to the new controller
    route.

    Closes-bug: 2039593

    Signed-off-by: Gustavo Pereira <email address hidden>
    Change-Id: Ibee0af9463092348578565bc489aa2025b00b0d5