nm team: Only show supported properties

[cathay4t]

Old code include everything get from teamd json config which
include unsupported options. The option link_watch might disappear
from time to time in teamd json config, this fails the verification
stage as the merge process will take this unsupported option to desired
state.

To properly solve that, only show supported properties:
* Team.Runner.NAME
* Team.Port.NAME

[coveralls]

Coverage remained the same at ?% when pulling ff5cb1a on cathay4t:team_hide into 30d9691 on nmstate:master.

[coveralls]

Coverage remained the same at ?% when pulling 76b6916 on cathay4t:team_hide into 220589a on nmstate:master.

[ffmancera]

Thanks! LGTM.

[EdDev]

Why should we limit the report? Is it wrong?
I do not understand.

If the problem is with the verification, then we should not merge unsupported properties there, not in the report. i.e. we should not merge read-only properties.

[cathay4t]

Why should we limit the report? Is it wrong?
I do not understand.

The update of teamd bring up bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1809050
https://bugzilla.redhat.com/show_bug.cgi?id=1808990

As we are showing arbitrary data read from teamd and that fail us on the merge and
verification.

If the problem is with the verification, then we should not merge unsupported properties there, not in the report. i.e. we should not merge read-only properties.

Unless start with _, people normally assume all showing data are supported and will be verified.
We are expecting github issue, bug report, customer support call if anything bug found for these unsupported properties caused by teamd changes.

[EdDev]

Unless start with _, people normally assume all showing data are supported and will be verified.
We are expecting github issue, bug report, customer support call if anything bug found for these unsupported properties caused by teamd changes.

nmstate may report read-only values that are not editable, this is a documentation or internal warning work that can be done. If team is unstable, it may cause issues indeed, but choosing almost all-or-nothing is too drastic from my taste.
Nevertheless, I will not insist on this as I have little interest in team at the moment.

Removing my vote.