clearify Bus On/Off handling after ChannelInit

In some situations the ethercat stack ignores a Bus_On-Packet. (e.g. not configured). The stack does not change the state.
The AP-Task acts on the returning packet and set Bus On/Off-Flag in the DPM.
E.g. BusOn in DPM is set then, but internally the Bus is not on (waiting for Bus On if no Autostart).

update:
How to handle BusOn/Off callback if stack is not configured?
-> do nothing (callback)
How to hande StartStopCommunication packets is stack is not configured?
-> reject with TLR_E_NOT_CONFIGURED (packet)