Resolve #189: Update ADT 3.0 Telemetry Schema for Statically Typed Language Compatibility

[kalosar]

Resolves Issue #189 - Schema Incompatibility with Statically Typed Languages

Summary of the Problem: The existing Telemetry JSON schema's multi-typed value field is incompatible with Java code generators that require a single type per field, leading to code generation failures.

Proposed Changes: This PR redefines the value field in the schema to be of a generic object type, accommodating the static type constraints of languages like Java. The field's description is updated to reflect the expected types, guiding developers on the intended use.

Modifications Made:

• The value field in the telemetry schema has been changed from multi-typed to a single generic object type.
• Documentation within the schema has been updated to specify that the value can be a number, boolean, or string.

Benefits of Change:

• Facilitates successful code generation for Java and other statically typed languages.
• Keeps the schema consistent across multiple programming languages and tools.

Updated Schema Details:

"value": {
  "description": "The value is expected to be a number, boolean, or string."
}