Fix X2Effect_Brutal by using GetCurrentStat() instead of GetBaseStat()

[boundir]

Fixes #1389

Fixes Brutal effect by using GetCurrentStat() instead of GetBaseStat().

[Iridar]

All Highlander submissions must follow the same comment convention.

For single line change, you would use // Single line for Issue #1389, and for anything more than one line, you would use // Start Issue #1389 and // End Issue #1389. Then there are Highlander inline docs, which get compiled automatically into this webpage: https://x2communitycore.github.io/X2WOTCCommunityHighlander/

They use a single /// HL-Docs: entry, and there are two types of those, one is used to document features, so they can be easier used by mod authors, and other uses to document bugfixes, and these are meant for mod users, and all get compiled into a single page: https://x2communitycore.github.io/X2WOTCCommunityHighlander/Bugfixes/

In case of single line bugfixes, it is acceptable to use a HL-Docs entry instead of "single line for issue".

Only one HL-Docs entry per issue is needed normally.

In this case comments would look like:

/// HL-Docs: ref:Bugfixes; issue:1389
/// Make `X2Effect_Brutal` use unit's current Will instead of base Will so it can properly reduce it.
// Single line for Issue #1389 - use GetCurrentStat() instead of GetBaseStat().
CurrentWill = TargetUnit.GetCurrentStat(eStat_Will);

and

// Single line for Issue #1389 - use GetCurrentStat() instead of GetBaseStat().
WillChange = NewUnit.GetCurrentStat(eStat_Will) - OldUnit.GetCurrentStat(eStat_Will);

[Iridar]

Perfect, though a bit annoyingly I have to ask you to squish the last two commits together, so there's still one commit with adding new files, and one commit where the issue gets actually resolved. This can be done via $git rebase -i HEAD~2 git command.