Add API mechanism for altering device status (Identity attributes 5/8) and signaling of application faults

User Story:

As a host application, I want to forward application specific fault states to the EtherNet/IP firmware so that the state becomes visible through EtherNet/IP means (Module Status LED and the corresponding Identity status (5) and state (8) attributes).

Background information:

With the V2 firmware generation, the host application had the possibility to set bit 8-11 of Identity status attribute 5.
This in turn also influenced the module status LED and state Identity attribute 8.

We need to provide a similar mechanism for the EtherNet/IP Core V3 generation.
In addition, the host application shall be able to modify bit 0 "Owned" and bit 2 "Configured".

Development Recap/Summary:

• Attributes 768 "internal status" and 769 "forced status" have been added to identity object
• Attribute 768 is the stack's internal status (formerly 5)
• Attribute 769 can be used to force specific bits in 5 from the host application side.
  Owned, configured and Fault bits can be altered.
• Major fault bits are deeply integrated with the module status, all others are non-functional.
• The major interface module towards device status is EIP_STATUS_*, which has been extended to consider the cases "host signaled fault" and "stack signaled fault" in a para-virtualized manner.
  Note the redundant definitions EIP_STATUS_HOST* to identity the host as the error source.
• Identity attributes are handled in the identity object whenever possible and escalate towards EIP_STATUS_HOST* on demand (e.g. fault bits)
• Features "LED forcing", "Exclusive host modification of attribute 8" and this new feature are partially overlapping functionally, though they are technically mostly independent mechanisms.