Port setting view/create are structurally asymmetric making updates arduous

The input to networking_switch_port_settings_create

https://github.com/oxidecomputer/omicron/blob/9df8ac02864f706c44b17831b2b55dda42178b1b/nexus/external-api/src/lib.rs#L5279-L5292

https://github.com/oxidecomputer/omicron/blob/9df8ac02864f706c44b17831b2b55dda42178b1b/nexus/types/versions/src/stronger_bgp_unnumbered_types/networking.rs#L264-L295

is structurally different from what we get from networking_switch_port_settings_view

https://github.com/oxidecomputer/omicron/blob/9df8ac02864f706c44b17831b2b55dda42178b1b/nexus/external-api/src/lib.rs#L5449-L5459

https://github.com/oxidecomputer/omicron/blob/9df8ac02864f706c44b17831b2b55dda42178b1b/nexus/types/versions/src/remove_duplicated_networking_types/networking.rs#L55-L83

What this means, is that when a user is trying to update switch port settings via the CLI, they need to fetch the settings in one format, do a mind meld with the OpenAPI specification or the underlying Nexus Rust data structures to figure out how to translate into the create format, implement that translation in JSON and then ship the updated json in the update request.