Description

This PR changes the behaviour of hosts regarding the Lobby service when they shutdown. Now, instead of leaving their lobby, they will delete it.

However, this makes it so clients who get disconnected afterwards will receive a LobbyNotFound error when trying to leave it. To prevent this, this PR also refactors how we handle Lobby exceptions, following the best practices outlined here. Now, instead of all being handled the same way in LobbyAPIInterface and always publishing errors, the responsibility is moved to LobbyServiceFacade. Since every call knows which errors to ignore and which ones to consider, it is each method's responsibility to determine how they handle LobbyServiceExceptions.

Issue Number(s)

MTT-4798 & MTT-4576

Contribution checklist

• [n/a] Tests have been added for boss room and/or utilities pack
• Release notes have been added to the project changelog file and/or package 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
• [n/a] An Index entry has been added in readme.md if applicable