fix: Antiban Breaks with different signatures

[Pauwelz]

Because of discrepancy between the documentation and the signature of TAntiban.AddBreak, certain issues popped up when either updating breaks in the form or reading them from the file with the interval and length being swapped.

As evidenced by running the examples\antiban_form.simba twice, once with defaults, once after loading presets:
{INTERVAL = 1800000, LENGTH = 120000, LOGOUTCHANCE = 0.01, STDVAR = 0.33, NEXT = 2153742.42903776, PREVIOUS = 0} {INTERVAL = 120000, LENGTH = 1800000, LOGOUTCHANCE = 0.01, STDVAR = 0.33, NEXT = 121432.544598551, PREVIOUS = 0}

By switching the parameters in TAntiban.AddBreak so it's in line with the documentation, this is resolved.
The json values used in TAntibanFormHelper.LoadBreaks also refer to the names instead of indexes now, so it's easier to indentify which value is being passed. This brings it in line with TAntibanFormHelper.LoadSleep.

[Torwent]

I was gonna say it was best to just update the docs so antiban form didn't need to get updated but I do like that you changed it to use the key names which makes it easier to spot future errors. Thanks!