Add flag to ignore mapflag restrictions in warpparty() and warpguild() script commands.

[Kenpachi2k13]

Pull Request Prelude

• I have followed proper Hercules code styling.
• I have read and understood the contribution guidelines before making this PR.
• I am aware that this PR may be closed if the above-mentioned criteria are not fulfilled.

Changes Proposed

• Added a flag to ignore mapflag restrictions in warpparty() and warpguild() script commands.
• Applied code style to warpparty() and warpguild() script commands.
• Updated doc/script_command.txt.

Issues addressed: #1861

[Asheraf]

So this silently breaks every script that relies on these commands checking the map restrictions, you can either introduce a flag to enable/disable these checks (defaults to enabled), or go with the suggestion in the related issue to deprecate these commands and merge them into warp().

[Kenpachi2k13]

There is no script that relies on that restrictions. warpguild() isn't used in any script and warpparty()is only used in F_CashPartyCall().
Furthermore; from my point of view, checking things like this is part of the script logic and should not be done inside the called function.
In my opinion, merging all warp commands into one seems to be a very bad idea. It would cause a parameter overload. And it would also cause that the meaning of one parameter depends on the value of another parameter (flag for passed ID is a guild or party ID) which isn't good programming practice.

[Asheraf]

I am not talking about the scripts included with the repository (those can always be fixed), but the tens of thousands of scripts written by the community since these commands were introduced a long long time ago, unfortunately opinions on how it should work does not matter here, the scripting engine MUST ALWAYS keep backward compatibility, unless you stop the script from loading you cannot change the behavior in a manner that breaks that compatibility.

[Kenpachi2k13]

Ah, okay. You're right. Thanks for pointing that out.
Requested changes are committed, please re-review.

As a side note:
The documentation for warpparty() implies that <include leader> can be passed without passing <from map name>, which is wrong but makes sense.
I'm indecisive, if I should repair this within this PR or in a new one when this one was merged.
Feel free to give an advice.

[Asheraf]

Hmm im not sure if i like inserting the new argument in the middle and that offset changing even though it works, anyways you missed updating the building definition with an extra optional argument.

[Kenpachi2k13]

I did not put the flag at he end of the argument lists, because this would force the user to pass a <from map name> (and for warpparty() also <include leader>), too, which makes no sense.