Intro cinematic sync

[Jannify]

https://cdn.discordapp.com/attachments/1038497385208365177/1120414323932680282/2023-06-19_20-03-44.mp4

[Jannify]

Syncing the cinematic and basic team-up/skip UI is done.

Notes on the state of this pr:

• The intro is disabled in DEBUG by default, edit MainGameController_ShouldPlayIntro_Patch for testing
• The intro works better with multiple lifepods but that is out of scope for this pr, mainly broken bc:
• Interacting with the lifepod by a third player (using hatch ladder, etc.) will hard cut the intro cinematic with unknown side effects. Therefor the server should spawn one lifepod per player pair/intro cinematic and it should be locked for other players
• We need a config options so big server can disable intro and spawning multiple lifepods

[NinjaPedroX]

Instead of locking the lifepods, have them fall out of the sky during the intro cutscene :)

[Measurity]

Code wise seems fine and working but did notice a side effect:

• On every join you get a "press to continue" screen which is different from master branch. I don't know if this was intended and if we want it. I personally prefer not to have the screen.

[tornac1234]

Encountered an issue for the second player who joined.
Also my two local players didn't start the cinematic at the exact same time. Maybe it could be made so that the packet sent from the server tells them to start at a precise timing like Time.now + 3 seconds (but it would change the packet structure).
Another issue to me is the fact that a player can't just skip waiting for a partner and start the cinematic without other people (let's say a group of 3 people want to play, 2 players will see the cinematic but the other one will be stuck).

[dartasen]

Works fine IG

[tornac1234]

Tests revealed it was good apart from the critical issue below

[tornac1234]

"partner" is not null even when the partner disconnects to fix that we can either:

• replace: partner != null by IsPartnerValid() in the two methods

private static bool IsPartnerValid()
{
    return partner != null && Resolve<PlayerManager>().Find(partner.PlayerId).HasValue;
}

• have the patch listen to PlayerManager.OnRemove, which might be a bit too much pain to find the right time to register and then to unregister the callback