[Request]: TECH DEBT: Refactor network resource management for 1.0.

[jglogan]

Feature or enhancement request details

We need to evolve our resource management in the client, API server, and plugins so that we have a maintainable codebase with good compatibility properties for 1.0.

The plan is to tackle this resource by resource, starting with Network. I've put together a checklist which will likely evolve as we work through this first resource:

• Conformance to ManagedResource (Create ResourceLabels and use for ManagedResource, NetworkConfiguration. #1360, Use NetworkResource for network management in API server. #1421)
• Client is an instance with init(servicePrefix:) that performs syntactic validation on all input (API: Rename to NetworkClient, client as instance. #1405)
• Client create(config:) -> FooResource (Use NetworkResource for network management in API server. #1421)
• Client list() -> [FooResource] (Use NetworkResource for network management in API server. #1421)
• Client get(id:) -> FooResource (Use NetworkResource for network management in API server. #1421)
• Client delete(id:) (Use NetworkResource for network management in API server. #1421)
• Server sorts list() results by resource ID (Sort networks by ID in API server list(). #1487)
• Client defines FooResource+XPC.swift with toXPC() -> XPCMessage and fromXPC(xpcMessage:) and round trip unit tests.
• Client defines FooService.swift protocol
• Server defines FooServing.swift protocol with FooService.swift implementation and FooTestService.swift implementation for round trip unit tests (for ensuring full XPC compatibility as API evolves).
• ListDisplayable conformance for CLI presentation in ContainerCommands (Use NetworkResource for network management in API server. #1421)
• No use of URL where FilePath should be used (#)
• 1.0 deprecation comments on all deprecated code (example: DEPRECATED 0.12.0 — retained for down-revision compatibility, remove in 1.0.0)

Code of Conduct

• I agree to follow this project's Code of Conduct