DESCRIPTION:
If a user opens the editor, loads a project from the cloud for the first time, does not / cannot sign in, and exits their project, a stub project is left behind locally that has none of the correct assets and is not actually linked to the cloud project. This stub project shows up as a local project in the Unity Launcher, but opening in shows an empty / default project that is not linked to the correct cloud project.

The user can manually link to the cloud project, but the result is that Collab thinks that the user has deleted/changed everything back to defaults and wants to push all those changes to the project (reverting the project to square one). The user can "revert" to the latest Collab push in order to fix their project, but this entire series of events seems extremely convoluted and probably shouldn't happen in the first place.

REPRO STEPS:
1. Have a project in the cloud but not locally (ex: you can create one locally, enable collab, upload it, delete local files)
2. Be in a scenario in which automatic sign-in to Unity Services will fail (ex: services failure, login issue, etc.)
3. Load the project from the cloud and wait for the editor to launch
4. Observe that the project is not actually loaded; the editor services tabs should show the user as offline
5. Close Unity
6. Re-enable sign-in to services (if you artificially disabled it)
7. Re-open Unity launcher
8. Observe that the project you attempted to load from the cloud earlier now appears as a local project
9. Load the local version of the project
10. After loading, sign in to services
11. Observe services tab

RESULTS:
"Stub" Project has none of the correct assets, and is not linked to the online version of the project

EXPECTED:
The "stub" project is deleted automatically, OR not shown (hidden) in the local projects list, OR can be opened and is properly linked to the appropriate cloud project so that connecting to services will start downloading the proper project assets

REPRO RATE:
10/10 on my setup (Windows 10)