[BUG/FEATURE] Fix Sysmessage Log Behavior / Add Override for `insysmsg` `waitforsysmsg` consumption

[ncskrypt]

Fix Sysmessage Log Behavior

• Increase log cap to 100. Trim by 5 when log exceeds cap.
• Only clear MATCHING log entries when waitforsysmsg if insysmsg returns true.
• Add ! Override for insysmsg waitforsysmsg to prevent any clearing/consumption.

  waitforsysmsg! (text) [timeout]
  if insysmsg!   (text)

Currently Razor clear ALL PRIOR messages in log INCLUDING UNMATCHED entries.

• Prevents checking same entry twice.
• Prevents checking completely unrelated messages appearing prior.
• Prevents checking common text in different messages, followed by additional checks.
• Prevents any meaningful use of waitforsysmsg 'text' followed by if insysmsg 'text' as it will return false.

Additionally, the message log is trimmed down to 15 anytime it exceeds 25+ messages.

• 25 is quite low of a cap. Wiping out 10/25 (40%) of the log seems excessive.
• Prevents checking important messages if repeated messages are spammed like "you must wait..." which is fairly common.

Relevant Code that handles this: https://github.com/UOOutlands/Razor/blob/14e5096e251e7d8fd9f7fb003818ff9df09b8cb6/Razor/Core/SystemMessages.cs#L30

public static void Add(string text) {
  if (string.IsNullOrEmpty(text)) { return; }

  Messages.Add(text);

  if (Messages.Count >= 25) {
    Messages.RemoveRange(0, 10);
  }
}

https://github.com/UOOutlands/Razor/blob/14e5096e251e7d8fd9f7fb003818ff9df09b8cb6/Razor/Core/SystemMessages.cs#L45

public static bool Exists(string text) {
  if (string.IsNullOrEmpty(text)) { return false; }

  for (int i = Messages.Count - 1; i >= 0; i--) {
    if (Messages[i].IndexOf(text, StringComparison.OrdinalIgnoreCase) != -1) {
      Messages.RemoveRange(0, i + 1);
      return true;
    }
  }

  return false;
}

[ncskrypt]

Issue with the code pushed recently for this enhancement.

It is only removing the first occurrence. It should remove all occurrences of that exact same message.