Lower the setup barrier for newbies

[NexiusTailer]

Current issues:

1. When you try to find releases of this repo, it's not shown in the right bar with quick sections. It is mentioned in the readme file and can be accessible by a link, but still you can't find it at first glance.
2. When you come to readme file, you immediately confused by the "mods" folder, where you allegedly should put .dll file, which mentioned in the Installation section (and this is relevant for both README.md and wiki page). Only after some research you understand that it's all about "modules" folder which you should create in "server/mods/deathmatch" to put king.dll there from the releases page.
3. After downloading amxdeploy.exe and resources/amx folder, running migration .exe tool and trying to lauch the server with ensuring to allow needed acl rights, you still stuck with the error (king.dll cannot be loaded). This is critical, because I can say for sure it was the main challenge to find the reason somewhere in the issues page, I almost gave up at some moment when I firstly found the possible reason about 32-bit server which were not relevant for my case, and only then found the second one about sqlite3.dll absence by default, so I downloaded it and it finally worked.

What it aims to change:
All binary files should be moved into releases page. Some attached archive with clear file structure and paths matching the current readme installation guide, with all needed .dll files in it. This way it will be intuitive to just jump into releases page, download everything in one click and unpack all those files in the root server folder without finding each file from different places or guessing where they to put in.

What should be changed specifically:

1. Toggle the releases section to be shown at main repo page (Edit repository details -> enable Releases checkbox in Include in the home page section)
2. Add an archive with king.dll / sqlite3.dll into the current release, so it will finally have all needed binaries archive in a single place to download (an example of the mentioned archive can be like this)
3. Considering the most common problems, add two notes in the latest release description:

• At the moment, AMX compatibility layer works only with 32-bit MTA server
• sqlite3.dll is missed in the current MTA server but required by king.dll to work properly

[Disinterpreter]

It is true, but before writing the guide we have to compile binaries for x64 because it is most popular server architecture.

My opinion is amxydeploy.exe must be deleted and some .html pages too which written many years ago they not valid today.

[NexiusTailer]

Speaking about popularity, I believe .so files then should be also compiled for linux server. But it's anyway up to the maintainers since even the current .dll presented as a very pre-release for test purposes only.

amxydeploy.exe seems not so useless, the very first setup when I tried it, it helped a lot to understand the paths and files structure which should be in practice, especially given that readme constantly made me confused with not so relevant information about where to put what. I think both migration tools .exe and perl script are better to stay in the repo, or maybe move to releases section (the binaries).

As for .html duplicate of the main repo readme, yeah, looks like it's just an old version with completely same information in it, but outdated. Already removed it in #96, hope everyone is agree that there is no need in such duplications when we have already README.md and a wiki page.

[colistro123]

I will be looking at this in a week. I'm in a seismic area with frequent earthquakes right now (Taipei) so pulling out the laptop is not a great idea, but will do ASAP.

[colistro123]

This has been addressed in the latest release. I hope this clarifies things.

[NexiusTailer]

Thank you for the solution! Now it seems to be in line with the current readme instructions and thus probably solves also each of those issues #55, #68, #72 and #74