Determine exactly which fields are and aren't required, and which are recommended

[thefinn93]

Currently test.py will fail if these fields are not present in any of the peering credentials:

• publicKey
• password
• contact
  And throw warnings (which don't show up very easily, see Better warnings in tests #20) if these fields aren't present:
• gpg
  Would people like to see these changed? I just kinda made these up while I was writing the tests script.

Other things to note:

• Currently almost none of the peers listed have a GPG key (I believe EU/se/stockholm/leeloo.kyriasis.com.k is the only one)
• The tests.py file has these fields defined in variables at the very top so it's trivial to change. Maybe eventually we'll even break it out into a proper config file.

[Kubuxu]

I think GPG should be optional, not everyone is using it but if it is present it would be nice if that fingerprint does not exist.

[kpcyrd]

I think gpg should be optional. Anway, we need to agree on a format. With or without spaces between blocks? Full fingerprint or id?

[Kubuxu]

For sure full fingerprint (for short ones there were keys generated for each).