fix: update binary-split repository

[reggi]

Updates the binary-split lookup entry to use the current max-mapper repository owner.

The package metadata published for binary-split@1.0.5 still points to maxogden/binary-split. npm/cli uses the CITGM lookup repository override when generating its integration matrix, preventing the stale codeload URL from returning a 404.

Addresses npm/cli#10020.

Validation: jq empty lib/lookup.json and git diff --check. The full test suite was not run.

[MikeMcC399]

This PR should have a commit message lookup: rather than fix:

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.20%. Comparing base (9697128) to head (83cf7a2).
⚠️ Report is 9 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1142   +/-   ##
=======================================
  Coverage   96.20%   96.20%           
=======================================
  Files          29       29           
  Lines        2213     2213           
=======================================
  Hits         2129     2129           
  Misses         84       84           

☔ View full report in Codecov by Harness.
📢 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[MikeMcC399]

I didn't notice this in time to add to this PR, however one of the maintainers (maxogden) of https://github.com/max-mapper/binary-split is no longer on GitHub.

@mourner is stil reachable, however there haven't been any repo updates since Dec 2023.

The package was last published to https://www.npmjs.com/package/binary-split as 1.0.5 on Oct 23, 2018.

Edit: see #1166

[MikeMcC399]

It also fails in Windows on all Node.js versions. Currently it is marked as flaky for Windows. It would be better to skip it for Windows instead. I'll follow up with a separate PR for this.

Edit: see #1167