Sphinx docs

[PerchunPak]

This PR merges sphinx-docs branch, so it wouldn't produce merge conflicts (like #465) as suggested @ItsDrike in Discord.

Note that documentation, in general, is not fully done. Parts (such as FAQ) are still in WIP. I'm also planning to add some "Quick Start" docs, simple examples, etc. but it's in my To-Do now.

There is also a still open conversation by @ItsDrike, which suggests removing mcstatus.dns from public API (see discussion on GitHub and in Discord).

So, this PR does not close the documentation To-Do - #136.

[PerchunPak]

Also, someone, please, resolve those merge conflicts in poetry.lock.

[PerchunPak]

Blocked by #478?

[ItsDrike]

Since this is merging to master, you can resolve the conflict here, with a merge commit (not with a rebase though, as you might want to rebase from our sphinx-docs if there are some changes, though I don't think there will be any until this gets merged).

[PerchunPak]

Since this is merging to master, you can resolve the conflict here, with a merge commit (not with a rebase though, as you might want to rebase from our sphinx-docs if there are some changes, though I don't think there will be any until this gets merged).

GitHub allows creating PRs even with branches, where you don't have push access. So I created py-mine:sphinx-docs -> py-mine:master.

I also can't change the source branch (sphinx-docs) to mine, without creating a new PR (or just GitHub UI says so).

[kevinkjt2000]

Wayyyyyyy better than what we have currently

[ItsDrike]

LGTM