[BUG] Salesforce: New Updated Field on Record triggers broken with certain Object-Field permutations

**Describe the bug**
Two of our registry Salesforce triggers only appear to be partially working - specifically, both the webhook and polling version of the trigger "New Updated Field on Record" only work in some cases.

Certain object-field permutations fail.
1. New Updated Field on Record (Instant, of Selectable Type)
2. New Updated Field on Record (of Selectable Type)

### To Reproduce
Use the account in shared 1P, michael@pipedreamsand...
Example workflow with working and broken triggers: https://pipedream.com/new?h=tch_3Z6fVy

#### Working Trigger configuration:
Contact/title

**New Updated Field on Record (Instant, of Selectable Type)**
1. Object Type: Contact
Field Type: Title
In the Salesforce instance, edit an existing contact, and change the Title. You should see the event fire successfully.

#### Broken Trigger configurations
Contact/title (polling), contact/email (webhook and polling)
1. The same object/field permutation does not work on the polling version:
**New Updated Field on Record (of Selectable Type)**

**New Updated Field on Record (Instant, of Selectable Type)**

2.
Object Type: Contact
Field Type: Email
A nondescript error, ```Error:
[object Object]
at s._deployWebhook (/var/task/node_modules/salesforce-webhooks/dist/index.js:1:138666)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async s._createWebhookWorkflow (/var/task/node_modules/salesforce-webhooks/dist/index.js:1:138844)
at async Object.activate (file:///var/task/user/sources/common-instant.mjs:34:23)
at async /var/task/index.js:95:13
at async captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:5)
at async exports.main [as handler] (/var/task/index.js:60:20)``` is returned when testing the Contact/Email permutation.

3. This is also broken with the polling source, as no events fire.

**Expected Behavior:**
1. I expect the polling trigger to fire an event when the field that is being watched on an object is changed.
2. I expect the webhook (instant) trigger to return an event for valid permutations, and return a more descript error message if there is something wrong with the setup.

**Notes:**
The Salesforce setup is complex and somewhat difficult to navigate; I added step-by-step instructions detailing the permissions required to configure webhooks in [our documentation](https://pipedream.com/apps/salesforce-rest-api#getting-started).