feat: Dedicated Game Server Sample - scenes and domain not reloaded [MTT-8055]

[fernando-cortez]

Description

PR to simply add to modify the project's editor settings such that Domain Reload is disabled.

Issue Number(s)

MTT-8055

Contribution checklist

• [ N/A ] Tests have been added for the project and/or any internal package
• [ N/A ] Release notes have been added to the project changelog file
• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• JIRA ticket ID is in the PR title or at least one commit message
• Include the ticket ID number within the body message of the PR to create a hyperlink

[RikuTheFuffs]

@fernando-cortez I don't see any change to classes that have static fields (I.E: ApplicationEntryPoint.cs , ServerPlayerSpawnPoints.cs and UnityServiceAuthenticator.cs). When domain reloads is disabled, static fields do not automatically clean up properly across Play runs.
Did you test running the game multiple times from the editor using different roles? (I.E: running as a server, then as a client)
If yes, does everything reset properly at the beginning of each run?

[fernando-cortez]

@fernando-cortez I don't see any change to classes that have static fields (I.E: ApplicationEntryPoint.cs , ServerPlayerSpawnPoints.cs and UnityServiceAuthenticator.cs). When domain reloads is disabled, static fields do not automatically clean up properly across Play runs. Did you test running the game multiple times from the editor using different roles? (I.E: running as a server, then as a client) If yes, does everything reset properly at the beginning of each run?

Yup exactly this. I tested all the scenarios, and tested their reconnection flows too. No errors, so it doesn't seem necessary to clean up any static fields.