Cannot link fork of private repository as Teams Pro user

🐛 bug report

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project
  adheres to.
• I have searched the issue tracker for an issue that matches the one I want
  to file, without success.

Description of the problem

Teams Pro account gets an error saying that I am not a patron when trying to link a fork to a any private repo.

How has this issue affected you? What are you trying to accomplish?

I just need a version controlled repo... Glitch does this really well.

To Reproduce

1. create a new pribate Sandbox from Node HTTP
2. export to new repo
3. create a sandbox from a fork of that repo
4. attempt to link that repo to the new forked sandbox

Link to sandbox: https://codesandbox.io/s/optimistic-lamport-yokc7?file=/src/index.js

Your Environment

Start by reproducing the issue using the listed steps with a private Node HTTP Sandbox and the linked sandbox at src/index.js. Trace the private fork linking flow and the Teams Pro entitlement check; the work is done when a fork of a private repository links without incorrectly reporting that the user is not a patron.