bug: blueos-core mangles host network settings on startup

### Bug description

When starting blueos-core container, it makes a bunch of destructive changes to the host network settings.

### Steps to reproduce

1. Start with a debian system that uses `NetworkManager` as the network manager. I believe a stock 64-bit Raspberry Pi Bookworm release will do.
3. Install blueos with the install script. If blueos is running, stop it with `docker container stop ...`
4. Bring up your network interface with `sudo nmcli d up enxb827eb81b20a` (your interface name will be different). Note this saves the network settings in a persistent file in `/etc/NetworkManager/system-connections/`.
5. In one window run `sudo nmcli monitor` to view network changes. Keep this running for the next step.
6. Start the `blueos` docker container and observe something like the below. Note too that the file created in `/etc/NetworkManager/system-connections/` has been deleted!
> ```console
> $ NetworkManager is running
> wifi0: connection profile changed
> wifi0: connection profile changed
> wifi0: connection profile changed
> wifi0: connection profile changed
> wifi0: connection profile changed
> enxb827eb81b20a: connection profile removed
> enxb827eb81b20a: deactivating
> Networkmanager is now in the 'connected (local only)' state
> Connectivity is now 'none'
> enxb827eb81b20a: disconnected
> Networkmanager is now in the 'connected (site only)' state
> 'wifi0' is now the primary connection
> enxb827eb81b20a: connection profile created
> enxb827eb81b20a: using connection 'enxb827eb81b20a'
> enxb827eb81b20a: connecting (externally)
> enxb827eb81b20a: connecting (externally)
> enxb827eb81b20a: connecting (externally)
> enxb827eb81b20a: connecting (externally)
> enxb827eb81b20a: connecting (externally)
> enxb827eb81b20a: connected (externally)
> Networkmanager is now in the 'connected' state
> Connectivity is now 'full'
> ```
>

### Primary pain point(s)

_No response_

### Additional context

_No response_

### Prerequisites

- [x] I have checked to make sure that a similar request has not already been filed or fixed.