AppFit Updated Track Event Payload

[claude]

This PR adds 6 new fields to the track event action:

 appVersion: {
      label: 'App Version',
      description: 'The app version',
      type: 'string',
      default: {
        '@path': '$.context.app.version'
      }
    },
    deviceManufacturer: {
      label: 'Device Manufacturer',
      description: 'The device manufacturer',
      type: 'string',
      default: {
        '@path': '$.context.device.manufacturer'
      }
    },
    deviceModel: {
      label: 'Device Model',
      description: 'The device model',
      type: 'string',
      default: {
        '@path': '$.context.device.model'
      }
    },
    deviceAdvertisingId: {
      label: 'Device Advertising ID',
      description: 'The device advertising ID',
      type: 'string',
      default: {
        '@path': '$.context.device.advertisingId'
      }
    },
    ipAddress: {
      label: 'IP Address',
      description: 'The IP address of the client',
      type: 'string',
      default: {
        '@path': '$.context.ip'
      }
    },
  osVersion: {
      label: 'OS Version',
      description: 'The version of the operating system',
      type: 'string',
      default: {
        '@path': '$.context.os.version'
      }
    },

Testing

Include any additional information about the testing you have completed to
ensure your changes behave as expected. For a speedy review, please check
any of the tasks you completed below during your testing.

• Added unit tests for new functionality
• Tested end-to-end using the local server
• [Segmenters] Tested in the staging environment

[tcgilbert]

@claude lgtm. this weeks action deploy just went out, so this will likely get deployed next week.

Meanwhile, if you have any questions or concerns, do let me know.

[claude]

Thanks @tcgilbert!

[joe-ayoub-segment]

hi @claude this PR has been deployed. Please confirm that you are happy with the change

[claude]

Well the change got implemented, but things are failing on our end because I put the version in the wrong spot in the payload. @joe-ayoub-segment Any chance we can do a hotfix, or do we need to address on our end and fix next week?

[joe-ayoub-segment]

hi @claude . Sorry to hear about that.
Is this causing issues for customers? Is there any data loss or corruption?
Best regards,
Joe