Fix Salesforce webhook event sources request verification

[js07]

In salesforce_rest_api/common-instant.js, the webhook token "x-webhook-token" was incorrectly destructured as undefined from event.headers following the codebase lint in commit e152f73.

This PR:

• Reverts this change and sets webhookToken to event.headers["x-webhook-token"]
• Bumps versions of Salesforce (Instant) sources

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployments, click below or on the icon next to each commit.

pipedream-docs-redirect-do-not-edit – ./docs

🔍 Inspect: https://vercel.com/pipedreamers/pipedream-docs-redirect-do-not-edit/DPSXoYn46YvTSUQDvADrQtRyYtFX
✅ Preview: https://pipedream-docs-redirect-do-not-edit-git-for-912549-pipedreamers.vercel.app

pipedream-docs – ./docs

🔍 Inspect: https://vercel.com/pipedreamers/pipedream-docs/H3B3oA9twte92s5Zodx7S2YqJtuL
✅ Preview: https://pipedream-docs-git-fork-js07-fix-salesforce-4c3402-pipedreamers.vercel.app

[dylburger]

• Create components to address specific use cases whenever possible
• Component keys should follow the format app_name_slug-slugified-component-name
• Components should follow the standard directory structure
• Prefer Node.js client libraries to REST APIs
• When making API requests, handle pagination to ensure all data / events are processed
• Use secret props to capture sensitive data
• Props and methods should be defined in app files whenever possible
• Document methods with JS Docs
• Use optional props whenever possible, and set a default value where you can
• Use async options to accept user input wherever possible
• Create subscription webhooks sources (vs polling sources) whenever possible
• Always emit a summary with events
• Use a built-in deduping strategy wherever possible
• When building webhook sources, follow these best practices
• When building polling soures, follow these best practices