Implement Timing Support

[RadWolfie]

I added support for a disable-timing config option to the config.txt file (which currently defaults to OFF). With timing log output enabled for each API's tests, we will know how long they took.

Here is a working example to see it in action:

with verbose:

327 - XeLoadSection: Tests completed in 162.254 seconds

without verbose:

327 - XeLoadSection: Tests completed in 1.048 seconds

Developers or testers can disable timing output by setting disable-timing=1 in the config.txt file. If a developer hasn't implemented KeQueryPerformanceFrequency and KeQueryPerformanceCounter APIs in their kernel, it is recommended to disable timing through config file or implement those APIs.

[ergo720]

If a developer hasn't implemented KeQueryPerformanceFrequency and KeQueryPerformanceCounter APIs in their kernel, it is recommended to disable timing through config file or implement those APIs.

You can use QueryPerformanceCounter and QueryPerformanceFrequency provided by nxdk to avoid that problem. Also, they are better anyway, since this PR has updated them to use RDTSC instead of KeQueryPerformanceCounter, which provides higher resolutions for timestamps (RDTSC uses the CPU frequency of 733 MHz vs KeQueryPerformanceCounter uses the ACPI frequency of 3.375 MHz).