Implement 802.1x (EAP) in network settings

[jcronenberg]

Problem

No option to configure 802.1x (EAP) for network connections.

Solution

Add ability to configure 802.1x in agama.
Note: For the certificates etc. NM supports 3 different formats. I decided to only implement the file format as that is IMO the most useful and should suffice.

Testing

• Added a new unit test
• Tested manually

sudo agama auth login && AGAMA_TOKEN=`sudo agama auth show`
curl -X POST http://localhost/api/network/connections \
    -H "Content-Type: application/json" \
    -H "Authorization: Bearer $AGAMA_TOKEN" \
    -d '{ "id": "ethernet-test", "method4": "auto", "method6": "auto", "ignore_auto_dns": false, "status": "down", "ieee-8021x": { "eap": [ "peap" ], "phase2_auth": "mschapv2", "identity": "test_user", "password": "test_pw", "client_cert": "/etc/NetworkManager/system-connections/cert.pem", "private_key": "/etc/NetworkManager/system-connections/key.pem", "private_key_password": "test_pw", "peap_version": "1", "peap_label": true } }'
curl -X POST http://localhost/api/network/system/apply \
    -H "Content-Type: application/json" \
    -H "Authorization: Bearer $AGAMA_TOKEN"
nmcli con show ethernet-test
# See 802-1x.* settings set.

[coveralls]

coverage: 71.803% (-0.03%) from 71.833%
when pulling 64d672f on jcronenberg:8021x
into ff3cf07 on openSUSE:master.

[imobachgs]

It looks quite good. Just a few comments. Thanks!

[imobachgs]

It would be great to describe each element of this section. For instance, ca_cert is described but identity is not.

[imobachgs]

Please, write some description. It will appear in our OpenAPI documentation.

[imobachgs]

If something goes wrong here, the whole service will crash.

[jcronenberg]

@imobachgs Thanks for the review. I think I should have addressed all your comments now.

[imobachgs]

Yes, thank you. Let's merge it.