Because:

- NAV 5.0 drops SNMP attributes as part of the Netbox model, introducing
  the concept of management profiles. Kindnavsync needs to be able to
  work with both pre-5.0 and post 5.0-versions of NAV for now.

Support for older NAV versions can be dropped later.

Also update to a trove license classifier that matches the actual license.

Viste seg vanskelig å debugge disse feilene mot en testserver :)

also ditch IPy in favor of ipaddress, which is built-in in Python 3

having timestamps in the log output will cause kindnavsyncdiff to trigger on
every run, even though the output is in fact the same.

if devices that exist both in Kind and NAV have differing rooms or equipment
types, update the NAV devices to be in sync with Kind.

if POSTing or PATCHing using requests, and the web server directs to a
canonical url (with a trailing slash), it looks like requests does not transmit
the payload a second time :P