Switching DHCP button in Network to Disabled causes loss of current IP

[chaul-ampere]

Describe the bug A clear and concise description of what the bug is.
Currently, I see that when DHCP is enabled, any action to configure a new Static IPv4 via Web will end up for it to become a DHCP-typed IP. There's no way to concurrently configure a Static IP and click the DHCP button at the same time. So after I added a Static IPv4 and turn the DHCP button to Disabled, BMC lost its IP and seemed to have to static IP to use.
To Reproduce Steps to reproduce the behavior:

1. Go to WebUI,
2. Click on Setting -> Network
3. Click Add Static IPv4 Address to add new Static IP X
4. Refresh WebUI
   => The Static IP X is now DHCP-typed
5. Click Add Static IPv4 Address to add new Static IP Y
6. Switch the DHCP button to Disabled
7. Refresh WebUI
   => Lost all the IPv4

Expected behavior A clear and concise description of what you expected to
happen.

• Commit e8cb2c6 Added DHCP enable/disable feature says that "DHCP when enabled, if there is no address, it picks up an address on its own. When it is disabled, we need to manually configure it. "I don't know if it means if I switch the DHCP button alone, I have to go to the BMC to directly configure a new IPv4 or anything. But I think that it should allow configuring a static IP before switching DHCP button to Disabled or keeping the old IP that DHCP provides as the Static IP to use.
  Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]: Window 11
• Browser [e.g. chrome, safari]: Chrome
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

• The only way for me to change the method to Static and still have an IP alive is to patch DHCPEnabled and add a static IPv4 at the same time through a Redfish command.
• Moreover, the "IPv4StaticAddresses" property in Redfish implements "http://redfish.dmtf.org/schemas/v1/IPAddresses.json#/definitions/IPv4Address", and the "IPv4Address" schema says in some of its properties including "Address" that "If DHCPv4 is enabled on the interface, this property becomes read-only". So I think it should avoid patching to "IPv4StaticAddresses" when DHCP is enabled unless DHCP is set to false along with the IP.