salesforce Add helper for validating and format input data

[mtuchi]

Summary

Add utils helper validateNoDotKeys and flattenData to help with validation of input data when using upsert, update or create and to transform nested object into a dot notation syntax when using bulk operation.

Fixes #556

Details

When mapping a salesforce data model there is a bit of confusion on when to use the dot notation and when not to. Since the best practice when mapping objects is to always use a nested object for relationship, it's important that the adaptor adds a safe check when you forgot and use the dot notation to map salesforce relationship. This PR adds two things

1. A validation step for upsert, update and create function. This is achieved by the new util helper validateNotDotKeys
2. A transformer to a dot notation syntax when using bulk function. This is done by the flattenData util helper

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to know!):

• Code generation (copilot but not intellisense)
• Learning or fact checking
• Strategy / design
• Optimisation / refactoring
• Translation / spellchecking / doc gen
• Other
• I have not used AI

You can read more details in our Responsible AI Policy

Review Checklist

Before merging, the reviewer should check the following items:

• Does the PR do what it claims to do?
• If this is a new adaptor, added the adaptor on marketing website ?
• Are there any unit tests?
• Is there a changeset associated with this PR? Should there be? Note that
  dev only changes don't need a changeset.
• Have you ticked a box under AI Usage?

[josephjclark]

Hey @mtuchi we need super clear docs on this to avoid confusion in the future.

I've updated the changeset to remove irrelevant stuff (users don't need to know about private internal APIs we've added) and to explain the changes. I've also added docs and example to each affected function.

Can you just check that this looks all correct? Any other suggestions as to how to best communicate this?

[mtuchi]

Thanks @josephjclark for the suggestions edit. I made tiny changes to the error message to give user more context if they want to map relationship records