fixes pod cryo

[harryob]

fixes #5863

🆑
fix: you can now enter cryo on pods
fix: cryo pods no longer tell you that they're broken
/:cl:

[SabreML]

I don't seem to be able to reproduce the issue locally on master. I assume I'm missing a step somewhere?
I can see the "It does not appear to be working" message on examine, but climbing into the pod seems to work normally whether it's docked, crash-landing, or flying in space.

[harryob]

I don't seem to be able to reproduce the issue locally on master. I assume I'm missing a step somewhere? I can see the "It does not appear to be working" message on examine, but climbing into the pod seems to work normally whether it's docked, crash-landing, or flying in space.

so, currently the state of the pods only changes when evac is declared/cancelled. somehow, #5683 managed to launch without the pod state being updated by evac being declared, not entirely sure how. it's easily reproduced using the shuttle manipulator, though. this just makes sure the pod state is correctly updated to LAUNCHED, instead of being on READY

[SabreML]

LGTM other than this for the COMSIG_PARENT_QDELETING handler.

[fira]

Needs destroy cleanup too of the list if the dock port is deleted
LGTM otherwise

[github-actions]

This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself