KM3NET BROADCAST_BASE don't reset wr_servo after announce timeout and don't set PortState to WRS_BROADCAST but stay in WR_PORT_CALIBRATION_8

KM3NET BROADCAST_BASE: Stay in WR_PRESENT state waiting for a targeted LOCK message and add some counters to test

concern DOMs (or other nodes) not concern the Bases. New additions will
come for Bases with BROADCAST_BASE statements.

KM3NET BROADCAST : - locking_enable in wr_link_on -> After unplug/plug or disable/enable the WR master port, the CLB stay locked in Uninitialized servo state because the spll stays locked.
		   - New WR state WRS_BROADCAST -> added for km3net monitoring via net.wr_st_gen variable.
		   - wr_servo_reset if errcount > 5 -> to play in a safe way.

KM3NET BROADCAST: We don't apply the HAS_FAULTS option with the broadcast configuration. We can enable the CONFIG_WRPC_FAULTS in parallel.

			If errcount > 5 set wrModeOn to False.

This modifications are needed because each time we reach an errcount > 5 (t1 timestamp flagged as
incorrect 5 consecutive times), we get stucked on uninitialized servo state.

KM3NET BROADCAST : Reset the timeout PP_TO_FAULT after receiving a follow-up message. Normally this is done after a response message, but we don't handle it.

KM3NET BROADCAST : set wrMode equal to WR_SLAVE in wr_handle_announce instead of wr_handshake_init (because in broadcast mode we never start the handshake).
		   + clear pp_lib_handle_announce.

KM3NET BROADCAST : Force the WRS_WR_LINK_ON after recive ANNOUNCE message in wr_handle_announce instead of pp_lib_handle_announce.

KM3NET BROADCAST : Reset the wr_servo if the TRACK_PHASE is not reached after a configurable number of iterations.