Additional drivers for working with VIM2

Improvements

• VIM did not use ARP to determine IP address uniqueness during the PROFINET Connection establishment.
• VIMNet Diagnostics introduced jitter in PROFINET RT frame production.
• The RPC endpoint mapper annotation string did not contain the correct information.
• Some network interruptions would prevent the VIM from attempting to reconnect to field devices.
• Under high load, data change would not always be reported to the DeltaV Controller.
• DeltaV Controller was allowed to set signal status under certain conditions. The signal status should always come from the VIM.
• VIM would report, via DCP, an invalid PROFINET name after it was first commissioned, but before a configuration was uploaded.