Move LED tests in x52test to the end

x52test doesn't perform any checks to see if the connected device
supports setting individual LEDs. Therefore, if an X52 (non-Pro) was
connected when running x52test, it would fail when running the LED
tests, and not perform any of the subsequent tests.

By moving the LED tests to the end, this allows the other tests to run
on a non-Pro X52. Although the tests would still fail, it won't actually
break anything.

Addresses #19.

utils/test/x52_test.c

@@ -85,11 +85,11 @@ static void signal_handler(int sig)
 
 #define TESTS \
     X(brightness, bri, "Test brightness scale (~ 1m)") \
-    X(leds, led, "Test LED states (~ 45s)") \
     X(mfd_text, mfd1, "Test MFD string display (~ 30s)") \
     X(mfd_display, mfd2, "Test MFD displays all characters (~ 2m 15s)") \
     X(blink_n_shift, blink, "Test the blink and shift commands (< 10s)") \
-    X(clock, clock, "Test the clock commands (~1m)")
+    X(clock, clock, "Test the clock commands (~1m)") \
+    X(leds, led, "Test LED states (~ 45s)")
 
 enum {
 #define X(en, kw, desc) TEST_BIT_ ## en,