0-delay DataPort/SignalPort bypass precedence rules

[ghost]

If a user sets a precedence rule between two InPorts:

inport1_.precedes(inport2_);

and either port is a 0-cycle delay, the precedence rule is ignored. The is the result of a design decision to enable fast callbacks from an Inport to the receiver bypassing the scheduler (which ensures the order). The precedence rule is still checked, but the ordering on the scheduler is ignored.

The fix for this is to keep a small state in the Port class that a precedence rule was established on the port. If a rule was set AND the port is 0-cycle, it must use the scheduler to deliver its payload.

This does not affect SyncPort.