Add an otpion to allow opcua metadata to be read

[codepitbull]

Motivation

Resolves #31480

Changes

• Add a config option to allow the retrieval of OPC UA tag metadata

[github-actions]

Test Results

  493 files  + 3    493 suites  +3   6m 45s ⏱️ +31s
4 188 tests +34  4 185 ✅ +34  3 💤 ±0  0 ❌ ±0 
4 218 runs  +47  4 215 ✅ +47  3 💤 ±0  0 ❌ ±0 

Results for commit 0cf4a7c. ± Comparison against base commit ede03cc.

♻️ This comment has been updated with latest results.

[github-actions]

Coverage Report

Overall Project	66.14% -0.08%	✅
Files changed	70.14%	✅

File	Coverage
BidirectionalOpcUaSpecificAdapterConfig.java	100%	✅
BuiltinJsonSchema.java	95.26% -0.91%	✅
OpcUaSubscriptionLifecycleHandler.java	81.39% -0.94%	✅
OpcUaProtocolAdapter.java	59.41% -0.58%	❌
OpcUaToJsonConverter.java	44.63%	✅
OpcUaSpecificAdapterConfig.java	36.14% -0.8%	✅
NorthboundTagConsumer.java	0% -23.91%	❌
JsonSchemaGenerator.java	0% -8.98%	❌

[mschoenert-hivemq]

There are a few things I would like to discuss here.

I don't understand why this is called "read-only" (not in this PR, but in the Feature request).
Certainly those properties are read-only, but many values (in OPC UA and in other protocol adapters) are read-only.
E.g. if you read the temperature from a sensor, you can't just write to that value to turn up the heat. ;-)
Unless somebody can explain to me why "read-only" makes sense,
I would suggest that we make a real effort to get rid of this misleading term!

I'm not super happy about the term Metadata either.
At least in the context of OPC UA, they never talk about these properties as metadata;
and there are other things (in the OPC UA specification) that are called metadata.

I'm also uncertain that this should be a toplevel attribute of the OPC UA configuration.
Shouldn't that rather be part of the tag definition?
E.g. as a user reading data from a OPC-UA device,
maybe I want these properties for some tags and not for others?

And finally, shouldn't we think about how this would look for other protocols?
Even if we have no plans to implement this on the current roadmap.

[marregui]

LGTM

[caoccao]

LGTM

[caoccao]

LGTM