fix auto_scheduler_network understanding dhcp_agents_per_network

[Sahid Orentino]

when using routed provided network there is condition which is bypassing the option dhcp_agents_per_network, which results that in a env with 3 agents and dhcp_agents_per_network=2, for a given network already well handled by 2 agents. if you restart the third agent It will start to handle the
network also which will result to have 3 agents handling the network.

The issue in under auto_scheduler_network function.

[yatin (yatinkarel)]

Fix Proposed:- https://review.opendev.org/c/openstack/neutron/+/910708

[Ihar Hrachyshka (ihar-hrachyshka)]

Could you please describe the exact scenario and behavior you deem incorrect re: routed networks?

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/neutron/+/910708
Committed: https://opendev.org/openstack/neutron/commit/1bc945f0d5f91f23ba6df617403b6b93ca1a4d98
Submitter: "Zuul (22348)"
Branch: master

commit 1bc945f0d5f91f23ba6df617403b6b93ca1a4d98
Author: Sahid Orentino Ferdjaoui <email address hidden>
Date: Fri Mar 1 10:05:35 2024 +0100

    dhcp: fix auto_scheduler_network understanding dhcp_agents_per_network

    When using routed provided network, the condition is bypassing
    dhcp_agents_per_network which results that in a env with 3 agents and
    dhcp_agents_per_network=2, for a given network already well handled
    by 2 agents. If restarting the third agent It will start to handle the
    network also which will result to have 3 agents handling the
    network.

    Closes-bug: #2058908
    Signed-off-by: Sahid Orentino Ferdjaoui <email address hidden>
    Change-Id: Ia05a879b0ed88172694bd6bffc6f7eb0d36bb6b0