Add Sentry failure callback to custom python operator

[sydneynotthecity]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• This PR avoids mixing refactoring changes with feature changes (split into two PRs
  otherwise).
• This PR's title starts with the jira ticket associated with the PR.

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or fixes.
• I've updated the README with the added features, breaking changes, new instructions on how to use the repository.

What

Airflow was not passing failed task status to Sentry correctly for del_ins_ tasks in the history_table_export DAG. The team was not getting notified when the task would fail, requiring manual inspection in Airflow to know if such tasks failed.

Why

I think the callback was defined too deep into the del_ins operator. There is an custom Python wrapper operator, called build_del_ins_operator that calls the actual operators that delete and insert data in BigQuery. The callback was set in the delete/insert operators, but not the Python wrapper. Adding to the wrapper to see if errors are sent to Sentry.

Known limitations

Needs testing in test to confirm that it works correctly.