When refreshing a connected sandbox, the source tracking is lost

**Describe the bug**
When refreshing a connected sandbox, the source tracking is lost.

**To Reproduce**
Steps to reproduce the behavior:
1. Refresh an existing sandbox on an active project/pipeline
2. When pulling changes from a Work Item, you are prompted to re-authenticate the DevOps Center connection
3. Once authenticated, no new changes are pulled, as if the source tracking connection is lost post refresh

**Expected behavior**
Once a sandbox is refreshed, it is expected to re-authenticate, but the hope is that this re-authentication would reconnect the source tracking, clear out the past source tracking log, and start tracking new changes

**Screenshots**
N/A

**Additional context**
Is the best practice to not use a Project for evergreen modifications? We typically do our work as first-in/first-out and not necessarily Project based, so our sandbox refreshes do not follow a specific cadence aligned with full Project go lives.