Fix type comparison in NumericRange.writeToValueAtRange

[kevinherron]

Allow boxed update values to be written into primitive current values and primitive update values to be written into boxed current values.

fixes #1476

[Copilot]

Pull Request Overview

This PR ensures that NumericRange.writeToValueAtRange can apply updates between primitive and boxed arrays by comparing boxed base types and instantiating the new array with the correct component type.

• Added getBoxedType to ArrayUtil (with tests) to normalize primitive vs. wrapper types
• Updated writeToValueAtRange to use getBoxedType for type checks and to instantiate the result with the original array’s component type
• Added tests in NumericRangeTest for writing boxed updates into primitive arrays and vice versa

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
stack-core/src/test/java/.../ArrayUtilTest.java	New parameterized tests for getBoxedType
stack-core/src/main/java/.../ArrayUtil.java	Implemented getBoxedType and updated copyright year
sdk-server/src/test/java/.../NumericRangeTest.java	Tests for primitive↔boxed update handling
sdk-core/src/main/java/.../NumericRange.java	Use getBoxedType in type comparison and adjust array instantiation and loop

Comments suppressed due to low confidence (1)

opc-ua-sdk/sdk-core/src/main/java/org/eclipse/milo/opcua/sdk/core/NumericRange.java:225

• The exception message prints the array objects instead of their types. It would be clearer to include the class names, e.g. currentType=%s, updateType=%s, currentType.getName(), updateType.getName()`.

String.format("currentType=%s, updateType=%s", current, update));