ci: Use 2i2c endpoint for triggering Binder build

[matthewfeickert]

Description

• Use 2i2c as the endpoint to trigger the Binder build given it is the primary endpoint for the Binder federation.
  • The Turing Institute no longer contributes to the Binder federation through compute resources.

Checklist Before Requesting Reviewer

• Tests are passing
• "WIP" removed from the title of the pull request
• Selected an Assignee for the PR to be responsible for the log summary

Before Merging

For the PR Assignees:

• Summarize commit messages into a comprehensive review of the PR

* Use 2i2c as the endpoint to trigger the Binder build given it is
  the primary endpoint for the Binder federation.
   - The Turing Institute no longer contributes to the Binder federation
   through compute resources.
   - c.f. https://mybinder.readthedocs.io/en/latest/about/federation.html

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.23%. Comparing base (126e83b) to head (d337632).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2636   +/-   ##
=======================================
  Coverage   98.23%   98.23%           
=======================================
  Files          65       65           
  Lines        4190     4190           
  Branches      453      453           
=======================================
  Hits         4116     4116           
  Misses         45       45           
  Partials       29       29           

Flag	Coverage Δ
contrib	98.11% <ø> (ø)
doctest	98.23% <ø> (ø)
unittests-3.10	96.42% <ø> (ø)
unittests-3.11	96.42% <ø> (ø)
unittests-3.12	96.42% <ø> (ø)
unittests-3.13	96.42% <ø> (ø)
unittests-3.9	96.46% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.