Unit and scale in schemas

Schemas are missing the unit and scale for each values.

For each value, add two fields:

• Unit (metre, degree, etc.) as in ETSI's asn1 description
• Scale

Example:

...
"latitude_value": {
      "type": "integer",
      "description": "Latitude of the geographical point.",
      "unit": "degree",
      "scale": 0.0000001,
      "default": 900000001,
      "minimum": -900000000,
      "maximum": 900000001
    },
...

In CDD:

/**
 * This DE represents the absolute geographical latitude in a WGS84 coordinate system, providing a range of 90 degrees in north or
 * in south hemisphere.
 * The specific WGS84 coordinate system is specified by the corresponding standards applying this DE.
 *
 * The value shall be set to:
 * - `n` (`n >= -900 000 000` and `n < 0`) x 10^-7 degree, i.e. negative values for latitudes south of the Equator,
 * - `0` is used for the latitude of the equator,
 * - `n` (`n > 0` and `n < 900 000 001`) x 10^-7 degree, i.e. positive values for latitudes north of the Equator,
 * - `900 000 001` when the information is unavailable.
 *
 * @unit: 10^-7 degree
 * @category: GeoReference information
 * @revision: Editorial update in V2.1.1
 */
Latitude ::= INTEGER {
    unavailable(900000001)
} (-900000000..900000001)

Begin by locating the project’s schemas and the CDD-derived value definitions referenced in the issue, then compare each value with the corresponding ETSI ASN.1 description. Add unit and scale metadata consistently across all schemas, and verify that every value has both fields with values matching its documented representation.