Reduce noise of INFO messages when sending large bursts

[Paebbels]

Currently, AXI4 models like Axi4Transmitter are emitting INFO messages on every sent AXI4-Stream beat, e.g. when sending Ethernet frames. Especially sending jumbo frames as a burst operation create easily >1000 lines of INFO messages per frame (8..9kB frames using a 64-bit AXI4-Stream -> 1024 cycles). Thus, logs are filled by INFO messages and simulators like Riviera-PRO can't scroll to the begin of the simulation log, due to log length limitations :(. Searching/finding relevant information in the log is slow and currently only HTML-ized logs can be inspected.

INFO messages can be disabled globally or in the transmitter model, but some INFO output are still useful. Especially when using burst operations.

Suggestion:

• Burst operations like SendBurst should trigger the model to emit one message at the begin of the burst and one message at the end of the burst.
• Burst operations on other models should be check if this usecase can be applied there too.
• Other mass-operations should be checked as well if this usecase applies there too.

Possible alternatives:

• SendBurst could be used 2 times, but this triggers 2 last-bits.
  I'm not aware of a SendBurst, that doesn't create a last-bit.
• Words could be send manually in a loop, but then burst FIFOs, incremental/random data generations can't be used.

Further suggestions:

• A model could offer a separate AlertLogID, which would allow fine grained control.
• A model's log classifications could be reviewed. As currently every transaction emits an INFO, this is actually a DEBUG or even TRACEing feature.