prefer_typed changes the values of strings

[Bre77]

Getting typed values from Fleet Telemetry with prefer_typed is great, but I wanted to check that it was meant to be changing the string values to different string values too.

For example
Sentry Mode has changed:
Off is SentryModeStateOff
Idle is SentryModeStateIdle
Armed is SentryModeStateArmed
etc

These already had pretty good values
, but now the protobuf field names are being returned

[jbanyer]

In addition: not all enum fields are being handled consistently, eg with the JSON format, vehicle version 2024.44.25.4 ad52e3119f65:

With prefer_typed = false:

      {
         "key":"ChargePortLatch",
         "value":{
            "stringValue":"Engaged"
         }
      },
      {
         "key":"DetailedChargeState",
         "value":{
            "detailedChargeStateValue":"DetailedChargeStateCharging"
         }
      },

With prefer_typed = true:

      {
         "key":"ChargePortLatch",
         "value":{
            "chargePortLatchValue":"ChargePortLatchEngaged"
         }
      },
      {
         "key":"DetailedChargeState",
         "value":{
            "detailedChargeStateValue":"DetailedChargeStateCharging"
         }
      },

Notice that DetailedChargeState is handled the same way regardless of prefer_typed, whereas ChargePortLatch is represented differently based on prefer_typed.

Is this going to change with future software releases? What is the recommended approach to handling enum values?