Incorrect treatment of IndexRange in Read/Write and Subscription services
Read/Write services were not returning Bad_IndexRangeNoData in case the index range was provided for a 1 dimension array and the value was not an array.
Subscription services:
- Notification were not filtered with the given IndexRange for MonitoredIem except for first Notification on creation
- Data changes were evaluated and sent based on the filtered value provided by write service instead of final value after write operation