Fix MinClientReqCheck and improve resource upgrade

[Fernando-A-Rocha]

Details

I found that MinClientReqCheck was not working on any builds because if was checking MTASA_VERSION_TYPE which not defined, due to a missing version.h import. I have restored this include in server StdInc.h, as it was back in the day (before a big refactor that removed this by mistake, see #3853 (comment)).

Also, I changed the Resource Upgrade feature to create min_mta_version with the "both" attribute when the client & server versions to set are the same (CResourceChecker.cpp). Attribute "both" is already correctly supported on resource parsing/loading.

Test

Tested by commenting the MTASA_VERSION_TYPE checks at MinServerReqCheck and MinClientReqCheck so this can run on custom builds:

Place this code on client.lua and server.lua script files in a new resource.

fileGetContents("doesnt_matter")

Start the server to load all resources or start the resource if the server was already running.

The resource upgrader will detect the missing min_mta_version information due to this new 1.6.0 function being used, which was added in 1.6.0-9.21938 for both client and server.

The upgrade command will result in the meta.xml being successfully updated with the new "both" min_mta_version required.

[Nico8340]

Perfect so far!

[Fernando-A-Rocha]

Some facts

Regarding resource upgrader:

I found that the upgrade command can only upgrade resources by setting a new min_mta_version client/server setting via the CResourceChecker::CheckVersionRequirements function that depends on client and server min versions listed in CResourceChecker.Data.h

Other older warnings like fetchRemote, callRemote etc cannot be automatically resolved with upgrade

They only pollute the debug console until the developer manually does something about the script(s).

[Fernando-A-Rocha]

Perfect so far!

I'm gonna look into what you said on discord: