No boundry checkings on RPI values when serving Adapter class3 ForwardOpen

With respect to EIP scanner API: There are two ranges of the connection packet intervals are defined:

1. [1000..32767000]uS for class1 connections
2. [1..3600000]mS for class3 connections

The valid RPI range for calss3 connections won't be checked when an adapter recevies a ForwardOpen request. This mostly causes problem in timer creation in the stack.
The stack also rejects the request with Extended Eroor code 0x011 (PRODUCTION TRIGGER NOT SUPPORTED) which is meaningless in this conetxt.

Also, the ulRpi resolution in EIP_OBJECT_OPEN_CL3_REQ shall be changed to microseconds to be more consistent between different packet services that hold an RPI value.