Using the /gamespace endpoint for long running tasks causes timeouts.

[sei-rguttman]

The current implementation of the /gamespace endpoint is synchronous - it doesn't return until the task is complete. For larger gamespaces or when the underlying virtualization server is under load, this can be a long running task and cause other middleware layers to inject a 500 error.

Another endpoint that allows for asynchronous deployment of gamespaces with a "I'm working on it, here's your gamespace ID" style response, which allows for the consumer to check back on the status of their deployment would allow us to prevent these cases.