Two slave/backup ports shall exchange WR messages. Trying to make this
work

Modifying switchover's ppsi to use ppsi and p2p. This is a temporal
branch...

[PSU] added functions to directly control PSU -- this needs to be done nicer, for the time being it works

master port on GM should copy DefaultDS.clockQuality (e.g. clockClass)
to ParentDS.grandmaster.clockQuality so that it is send out in Announce
messages. BC should not do that, as it copies clockQuality received
on the slave port into the ParentDS.grandmaster.ClockQuality and sends
out on its master ports this info.

presumably-bug commented out: some-kind of holdover degradation of ClockClass done in very bad place

The degradation of class should be managed more globally, is specific
to holdover (which is now being implemented) and should not inform about
unlocking if no holdover implemented. Will be remmoved once holdover
works.

m1() was used always when entering MASTER on Announce timeout - this
caused  "comming up" port (which usually enters MASTER) to use m1()
to overwrite the parentDS->grandmasterClockClass with its local
ClockClass. This should not happen on BC which is already synchronize.

instead of GM clockQuality info, the information from Default DS
was sent in announce. Corrected according to Table 25, p129 of PTP

bugfix: the classClass of a current GM was overwriten by the default clockClass each time new port went up

the bmc data copying functions (e.g. m1(), s1()) should be called only as a result of BMCA. This is rather irrelevant for WR, but important
for PTP networks

bugfix of multi-backup servo: now the active port is updated only in precise moments so if we update the phase of the backup, it will finish the process before switchover is registered

fixing bug with a hack -> making got_sync static variable multi-port friendly (one was shared by many ports, no it is a table)

including prio=0 into priorities allowed for backup ports (correcting nasty hack without diminishing its nastiness)

messing up with BMCA for WR - not sure it will be used like that, need to move to WR-specific if stays

added new global config option, not very good way, to be revised (global ext-specific stuff in non-ext-specific code)

new priority scheme (priorities passed when locking)
 prio 0 : one one port can be slave)
 prio >1: if priorities equal, first connected is active, rest backup
          if priority lower, it becomes active