Fix incorrect key mapping on macOS with vanilla ctrl detector

[TonyCrane]

What

On macOS, command ⌘ is used as Ctrl, but the key code of command ⌘ is different. Instead, control ⌃ has the same key code as Ctrl.

So for those classes using GTUtil, users should press control ⌃ to represent Ctrl, which is weird.

This PR reuse vanilla MC's hasControlDown method to deal with "Ctrl" on different platforms, letting macOS users to press command ⌘ for Ctrl.

Implementation Details

Vanilla MC's hasControllDown checks platform, if on macOS, then treat GLFW_KEY_LEFT_SUPER (which is command on macOS) as "Controll":

// in net.minecraft.client.gui.screens.Screen
   public static boolean hasControlDown() {
      if (Minecraft.ON_OSX) {
         return InputConstants.isKeyDown(Minecraft.getInstance().getWindow().getWindow(), 343) || InputConstants.isKeyDown(Minecraft.getInstance().getWindow().getWindow(), 347);
      } else {
         return InputConstants.isKeyDown(Minecraft.getInstance().getWindow().getWindow(), 341) || InputConstants.isKeyDown(Minecraft.getInstance().getWindow().getWindow(), 345);
      }
   }

Since the vanilla MC has such an interface, I think there's no need for us to implement another one using the underlying GLFW interface.

So I replace the logic of isShiftDown isCtrlDown isAltDown with vanilla's hasShiftDown hasControlDown hasAltDown to make the code cleaner and more robust.

And unfortunately, ldlib also use GLFW's interface to check these keys in ClickData and no checks of platforms. So I write a new mixin to change the value of isCtrlClick to make sure the packet sent from client is correct.

Outcome

On macOS, users will use command as Ctrl. And on other platforms, there is no changes.

How Was This Tested

I have run runClient to ensure this works well on MacBook keyboard.