Bug: The ending of the CTF resets the state of a user's virtual env access even when the env is still running.

[UsakoSenpai]

Problem:

• The ctf ending/closing causes the status of the virtual environments to be lost and users no longer have the ability to destroy, restart, download private key, or get connection info from their user profile screen. It resets to the beginning of the CTF state even though the virtual env is still running.

Screenshots / Evidence:

The profile page no longer indicates or provides info on the virtual env:

The virtual env is still up and can be SSH'd into:

Expected result

• The profile page maintains the active/current state of the virtual environment regardless of the status of the CTF (having ended or not)

Steps to Reproduce

1. Have the CTF be in an active, running state.
2. Start up a user's virtual environment.
3. Have the CTF complete/end and be in a non-running state.
4. Refresh the user's profile page and observe the virtual env state now appears to be reset as though not started/running.
5. Verify the user is still able to ssh/access the virtual environment and that it is still running.