[nezuo]

Closes #305.

I typed and reviewed all the code but I used AI as an assistant.

I recently became aware that you can pass a script to run as a Roblox Studio CLI flag: Source.

This allows us to implement this feature in a much more robust way than #896.

Unfortunately, the script is printed to the output but I can live with that:

This supports partially-managed, fully-managed, and cloud places.

Unlike the old version, I did not include the initial sync skip for the sake of simplicity. I'm open to discuss adding it.
Universe ID is required now and there is no port randomization anymore.

Implementation Notes:

• UserId is used for Team Create so that you don't read/delete someone else's rojo open request.
• We verify the session id to avoid edge cases like stopping the serve before studio fully opens and starting a new serve with the same address/port.

Open Questions:

• There is no behavior to delete the temp file containing the script source. Should this be done?
• I decided to not bypass the sync confirmation. Should this change or could it be a CLI flag?
• There is a security concern where a plugin could insert a ROJO_OPEN instance to connect to a malicious server. We could limit rojo open to only loopback. What do we think here?

[nezuo]

Thinking more on my usecases, I would want to skip the confirmation dialog for rojo open. Not sure if that should be the default, a CLI flag, or maybe a plugin option specifically for rojo open.