fix: log error response in case of tenderly node non 200 http status

[jsy1218]

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  Bug fix

• What is the current behavior? (You can also link to an open issue here)
  Besides small amount of tenderly API vs tenderly node response mismatch, I noticed small amount of TenderlyNodeGasEstimateBundleFailure.

This is due to:

If I hit against the same tenderly node endpoint with the same payload, I got a result array:

{"id":1,"jsonrpc":"2.0","result":[{"error":{"code":3,"message":"execution reverted","data":"0x"}},{"gas":"0x77e6","gasUsed":"0x77e6"},{"gas":"0x29cee","gasUsed":"0x23bac"}]}%         

This tells me that Cannot read properties of undefined (reading 'length') from reading resp.result.length is a sporadic runtime error, most likely because tenderly returned a non-200 status code.

• What is the new behavior (if this is a feature change)?
  If tenderly node returns non-200, we want to log that response as error.

• Other information:

[jsy1218]

• fix: log error response in case of tenderly node non 200 http status #620 👈
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jsy1218 and the rest of your teammates on Graphite

[graphite-app]

Graphite Automations

"Request reviewers once CI passes on smart-order-router repo" took an action on this PR • (06/27/24)

4 reviewers were added and 1 assignee was added to this PR based on 's automation.

[jsy1218]

Merge activity

• Jun 27, 7:15 PM EDT: @jsy1218 started a stack merge that includes this pull request via Graphite.
• Jun 27, 7:15 PM EDT: Graphite couldn't merge this PR because it failed optional checks and "ignore optional checks" was not selected.
• Jun 27, 7:51 PM EDT: @jsy1218 started a stack merge that includes this pull request via Graphite.
• Jun 27, 7:55 PM EDT: @jsy1218 merged this pull request with Graphite.