Authentication on the client side

[viacheslauK]

Brief:

This pull request introduces changes to the client-side of the OPC UA module in accordance with the Authentication Modelling Guide. When a user does not have sufficient permissions to read, write, or execute, the corresponding properties and attributes of openDAQ entities are set accordingly. Additionally, the behavior of certain methods is adjusted based on the user’s permissions.

Description

• Function and Procedure calls return proper error code on client side if user access denied;
• readOnly flag for properties on client side if there is no write permission;
• set a method property as invisible on client side if there is no execute permission;
• BeginUpdate and EndUpdate methods return proper error code on client side;
• object attributes locking on client side if there is no write access;
• getAvailableFunctionBlockTypes method returns an empty list on client side if there is no write permission (only for a device);
• setOperationMode and setOperationModeRecursive methods return proper error code on client side;
• acceptsSignal method returns false on client side if there is no write permission;
• tests;

Known issues

• getAvailableFunctionBlockTypes method has not been implemented for FunctionBlock;
• getAvailableDeviceTypes and getAvailableDevices methods have not been implemented for Device;
• lock and 'unlock' methods have not been implemented for Device;

[denise-opendaq]

looks good to me. just need small changes :)

[denise-opendaq]

super puper :)