Unsure what to do about the facade path for moved repos

When we detect a repo has moved (301), we create a new dict of repo table data with the `repo_path` set to `None`

https://github.com/chaoss/CollectOSS/blob/115b4eec7c2d08d1bda4cef60c2c4c3dd8ea9546/collectoss/tasks/github/detect_move/core.py#L112

This line was last touched in 34d5c7db2c10af03faf8c650a6197198bd4031fa

We do this without resetting the facade collection state such that it will be cloned fresh next run, which essentially breaks collection/puts facade in a weird state.

Start at collectoss/tasks/github/detect_move/core.py around line 112 and trace how the facade collection state is handled after a 301 redirect. Reproduce the next collection run for a moved repository, then verify that the repository data and facade state no longer leave collection broken or in an inconsistent state.

Written by the indexing model from the issue text.