[API change] - For setting data into a config assembly, use packet *OBJECT_CHANGE_IND instead of *CL3_SERVICE_IND.

For historical reasons, whenever data is set into a config assemblies, may it be due to explicit set access or due to opening of an I/O connection with configuration data towards that assembly, the data was presented to the application by means of packet CL3_SERVICE_IND.

Thus, attribute 3 of config assemblies has been treated inconsistently when compared to all other attribute values, for which the OBJECT_CHANGE_IND is generated on change.

With this ticket, the implementation is changed, so that data set into a config assembly is now presented to the host application with packet OBJECT_CHANGE_IND instead of CL3_SERVICE_IND.

Therefore, the indication's response CIP_OBJECT_CHANGE_RES was altered, so that the application can now return a set of CIP error codes to the CIP client, respectively. This equals the capabilities of CL3_SERVICE_IND.

Subsequent to this change, CL3_SERVICE_IND will only be used for user-registered objects and services., whereas OBJECT_CHANGE_IND will be used for all attributes of built-in objects and services.