Http & Salesforce improvements

[mtuchi]

Summary

Add callback support for parseXML in http and add options and callback support for query in salesforce

Details

Callback is very useful especially when it's used in each() function. The callback support in parseXML will make it easier to pluck out data from state.data.body. See example below

each(
  "$.response[*]",
  parseXML(
    (s) => s.data,
    ($) => $,
    (next) => ({ ...next, results: next.data.body })
  )
);

For salesforce i made some improvement for the query function to use query(qs, options, callback). This will allow me to specify options like { autoFetch: true } which will make it easy to query more records using only the query() instead of bulkQuery()
Eg:

query('SELECT Id, Name from Account, { autoFetch: true });

With the given example above ⬆️ , If the results is more 2000 records. Then the function will auto-fetch the remaining records until we have all records

Closes #394, #447

Review Checklist

Before merging, the reviewer should check the following items:

• Does the PR do what it claims to do?
• Are there any unit tests? Should there be?
• Is there a changeset associated with this PR? Should there be? Note that
  dev only changes don't need a changeset.

[mtuchi]

The failing tests are related to mailgun, See #477 for more information

[josephjclark]

@mtuchi this looks great. Can you please rebase (or merge) against main and run pnpm changeset version to push version changes? Then we can merge this in.