CONSENT-309: Ensure consent data is copied for Segment Connections + Profiles

[chenxzhang]

While working on consent in RETL, we realized that the event's context.consent.categoryPreferences data isn't copied over. This PR adds the data to the track events for Segment Connections + Profiles.

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

Tested the change in stage and verified the events in Segment Connections + Profiles have the consent data.

Segment Connections:

Segment Profiles:

[joe-ayoub-segment]

hi @chenxzhang thanks for raising this PR.

Here's some feedback and questions.

1. I can't see why the yarn.lock file was edited. Was this a mistake? If so can you please rectify?

2. Is your intent to grab andinclude the entrire object from the context.consent location? If so that's all good. Is there a partticular schema that this data should look like? Should we validate it in any way? If so, I can show you how to do this.

3. Could you please attach evidence of testing howing what the context.consent object looks like please?

[chenxzhang]

hi @chenxzhang thanks for raising this PR.

Here's some feedback and questions.

1. I can't see why the yarn.lock file was edited. Was this a mistake? If so can you please rectify?
2. Is your intent to grab andinclude the entrire object from the context.consent location? If so that's all good. Is there a partticular schema that this data should look like? Should we validate it in any way? If so, I can show you how to do this.
3. Could you please attach evidence of testing howing what the context.consent object looks like please?

Thanks for the review!

1. I was getting CI error and had to do yarn install https://github.com/segmentio/action-destinations/actions/runs/9393961071/job/25870870707

2. Yes. I want to grab context.consent.categoryPreferences. categoryPreferences should be an object/map of string: boolean.
   For example:

"context": {
    "consent": 
      "categoryPreferences": {
         "Advertising": true,
         "Analytics": false,
         "Functional": true,
         "C003": false
      }
    }
  }

3. I'll add them to the PR description

[joe-ayoub-segment]

Thanks @chenxzhang . I still think the yarn.lock file shouldn't change. Any chance you could rebase from main? it might fix that issue.

[varadarajan-tw]

The changes look good to me. Left few minor comments.

[varadarajan-tw]

I don't think addtionalProperties is necessary here would help considering the field is hidden.

[varadarajan-tw]

Same comment as above. additionalProperties are not required for this use case.

[varadarajan-tw]

Is this error being used anywhere?

[chenxzhang]

deleting it

Joe is out of office and the team needs this PR shipped. So, I am approving on behalf of Joe

[joe-ayoub-segment]

hi @varadarajan-tw has this been deployed?