[DOCS] Getting Started doc(s) for the Multiplayer Sample project

[chanmosq]

Describe the issue briefly

Would like to have a Getting Started guide to compliment the Multiplayer Sample project (MSP), which users can download and play around with.

Some questions to address may be

• What's a quick explanation of the intent of this project and its core features
• What are the simplest steps to install and set up the provided sample project. (Should user start with a blank project, or download the MSP? Any Gems to build with?)
• What are the most important questions new users will have?
• What are cool things users can do with this project?

Requests to include in this doc

• Add as a prerequisite what the most stable version of O3DE to use with this project.
• Usage of CVARs and .cfg files. Can reference the CVAR docs in "Related topics".

Which page(s) / section(s) are affected?

The document should live in https://www.o3de.org/docs/learning-guide/tutorials/multiplayer/. We may need to split this to multiple pages.

Does this work have an engineering dependency? What is it?

Depends on knowledge of O3DE's networking features, and preferably knowledge from developer of project.

[chanmosq]

This task relates to #919 and #1318, as documentation on the MSP may reference Multiplayer docs .

[sptramer]

Declined for the following reasons:

• Multiplayer sample is not distributed as part of core O3DE, and is a separately maintained example project. It can be index on the website, but any instructions for the project itself must be self-contained documentation, ideally README.md.
• There is a forthcoming RFC to create a specific SIG for the maintenance of supplementary projects such as this one, to keep docs sig and the website from becoming overloaded/crowded.

@o3de/sig-ui-ux @o3de/sig-network - Tagged due to relevance of current MSP ownership and RTE tracking.

[lmbr-pip]

IMHO:

• READMEs cannot hold complex documentation, users do not read them anecdotally
• Repo wikis are hard to use because theres no process to make PRs, review changes and push them, which means that theres no valid collaboration flow that the community can own.

Also please link to RFC or public roadmap item for RFC otherwise, we should have a public item that we are punting to.

[yuyihsu]

this was defined as critical in the post-RTE discussion.

[sptramer]

Just because the website isn't the appropriate place for it, and this isn't the correct way to address the problem, doesn't mean it isn't critical.

[sptramer]

Closed in favor of o3de/o3de-multiplayersample#174