[dpazj]

Summary

Removes the parameters-only template workaround from the tck-node example and publishes a real template instance in the device birth instead of the node birth.

• Point has metrics x, y, z and the scale parameter again.
• The template definition is published in the node's NBIRTH via register_template::<Point>().
• The template instance is published in the device's DBIRTH by a new TckDeviceMetrics wrapper around the device's SimpleMetricManager.
• No template instance is published in NBIRTH.

Why

SendDataTest.checkInstance evaluates the payloads-template-instance-members-data assertion for every message type, even though the requirement only applies to NDATA/DDATA:

setResultIfNotFail(testResults,
    found && (msgtype.equals(DBIRTH) || msgtype.equals(NDATA) || msgtype.equals(DDATA)),
    INSTANCE_MEMBERS_DATA, ...);

For an instance in NBIRTH, msgtype is NBIRTH so the expression is always false, even when the instance contains every definition metric. The previous workaround avoided the failure by declaring a template with no metrics, which left the four member assertions NOT EXECUTED.

With the instance in a DBIRTH, msgtype is DBIRTH and the expression is found, so the assertion executes and passes.

Result

edge:SendDataTest         PASS   44 assertions: 44 passed   (was 40 passed, 4 not executed)
edge:SendComplexDataTest  PASS   48 assertions: 48 passed

All four template member assertions (definition-members, instance-members, instance-members-birth, instance-members-data) now run and pass.

cargo fmt --all --check, cargo clippy --all-targets -- -D warnings, and cargo test pass.