cli 2.0 unity reintegration

[gabrielbeamable]

Brief Description

After the removal of manifest file in the CLI 2.0, we needed to go back to Unity SDK and make sure it still works. That means:

• Removing all signpost files
• Making sure that projects are recognizable in UI and Unity solution in IDE
• Making sure the SDK knows if a service exists locally or just remotely

This also makes a few changes, like:

• Change the way the CLI loads the projects by instead of running dotnet processes to get projects properties, it will now use Microsoft.Build to load the projects and access it's attributes. This gives a significant improve in the load speed when running any CLI command.
• Fix bugs with paths being passed between the Unity SDK and the Microservice
• Remove a lot of unused code
• Updates the Unity CLI-generated code

There is a lot of commented code in this PR as well. A few features will need to be reworked after this update, such as referencing assemblies and the migration from older versions of the SDK. I felt like leaving most of it commented because the code might be helpful in the future.

Notes

When you are merging a feature branch into main, please squash merge and make sure the final commit contains any relevent JIRA ticket number. If you are merging from main to staging, or staging to production, please use a regular merge commit.

Does this introduce tech-debt? If so, have you added an entry to the Tech-debt document?

[github-actions[bot]]

Lightbeam link

[github-actions[bot]]

Lightbeam link

[github-actions[bot]]

Lightbeam link