[MCS-DE-GO] - Make local publishing an Async Operation

[joaollq]

When publishing locally from the Composer the application freezes until the dotnet build + dotnet run flow is completed.

There are several problems with this approach, namely:

• When the dotnet build takes longer >1 min (due to the nuget restore operation) the UI times out and gives an error stating that there was a problem with the runtime. Actually the process is still running server side.
• The user cannot navigate to other parts of the Composer app. The requests will receive a 502 Bad Gateway error after the timeout
• When running the composer in a hosted mode, the local publish process freezes the app for all users and not only for the user publishing the code

In my local publish plugin I tried to use the same approach as the other plugins, by putting all the build and run part in a different thread and returning a 202 Created response to the UI in the hope of seeing the UI polling the "get publish status" endpoint until a 200 OK is returned. Nevertheless it doesn't work that way as the local publish seems to be prepared to receive only 200 OK results.

@goergenj @benbrown @sgellock

[benbrown]

@VanyLaw we should take this into consideration as we update the runtime abstractions.

[benbrown]

This will be fixed by #3198.

[cwhitten]

Closing in anticipation of #3198