StackAdapt audience destination: Migrate destination to use mappingSchemaV2

[Vanessa-SSY]

A summary of your pull request, including the what change you're making and why.

• When calling upsertProfileMapping mutation, there's an argument mapping_schema which takes a JSON blob. We are migrating it to mapping_schema_v2. It has defined GQL types for better validation and security.
  It won't cause any issue if you keep using mapping_schema, but we want to deprecate mapping_schema at some point.
• update field mapping to include label

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
• [If destination is already live] Tested for backward compatibility of destination. Note: New required fields are a breaking change.
• [Segmenters] Tested in the staging environment
• [Segmenters] [If applicable for this change] Tested for regression with Hadron.

[joe-ayoub-segment]

Hi @Vanessa-SSY , thanks for the PR.

Please see the inline comment regarding the change to the package.json file.

I also noticed that the snapshot tests need to be updated as they are failing. Try this command:

yarn cloud test packages/destination-actions/src/destinations/stackadapt --updateSnapshot

Finally, do you have any proof of actual testing that this works with the new API? Would you be able to demonstrate that an end-to-end is able to send data through the two updated Actions? Some screenshots should be sufficient.

Cheers!
Joe

[joe-ayoub-segment]

Hi @Vanessa-SSY - I'm guessing you edited this file in error. Can you undo the change for this file please?