Reduce the scope of the network settings

We have a maintenance issue with the network settings. They have the most issues out of all the settings panels, and we don't have domain experts available to diagnose and fix issues as they come in. Looking at the issue tracker, it's hard to be confident that the existing network settings actually work.

Reducing the scope of the network settings is an obvious solution to this. We could have a more limited set of options, which get better testing and don't cover specialist features. For anyone who wants more than that, we can point them to nm-connection-editor (we would therefore need to fix #1157).

Of course, the question then becomes: what should the scope of the network settings actually be? I've come up with a preliminary answer to this, in order to try and move the discussion along. The answer there is, roughly:

In scope

• Basic settings for each connection:
  • Connect automatically
  • Available to other users
  • Metered connection
  • Change password (Wi-Fi only)
  • Change the connection name (all connection types except Wi-Fi)
• View the details of each connection: IP addresses, MAC address, gateway, DNS, etc
• Configure a static IP address

Out of scope

• Adding any type of connection, including:
  • Wired profiles
  • Hidden Wi-Fi networks
  • VPN connections
• Everything else from the connection properties, including:
  • All the other IP methods (link local, shared, etc)
  • Changing a MAC address
  • Security settings other than standard Wi-Fi passwords
  • Choosing between IPv4 and IPv6
  • Modifying VPN connections, including the gateway address and authentication