Enable TRACY_TIMER_FALLBACK for libTracyClient

This fallback is most likely to kick in on VM's that may not have
support for the rdtsc instruction.

The loss in timer fidelity can be pretty severe (8 ns -> 15.6 ms)
but we pack lots of other metadata into our traces, so it can still
be useful to run with the fallback (and forcefully crashing the
application as Tracy does now is just not the Julian way to
communicate a hard error anyway)

deps/libtracyclient.mk

@@ -15,6 +15,7 @@ LIBTRACYCLIENT_CMAKE += -DTRACY_NO_CODE_TRANSFER=ON
 LIBTRACYCLIENT_CMAKE += -DTRACY_NO_FRAME_IMAGE=ON
 LIBTRACYCLIENT_CMAKE += -DTRACY_NO_CRASH_HANDLER=ON
 LIBTRACYCLIENT_CMAKE += -DTRACY_ON_DEMAND=ON
+LIBTRACYCLIENT_CMAKE += -DTRACY_TIMER_FALLBACK=ON
 
 ifeq ($(WITH_TRACY_CALLSTACKS),1)
 LIBTRACYCLIENT_CMAKE += -DTRACY_CALLSTACK=32

deps/libtracyclient.version

@@ -1,6 +1,6 @@
 ## jll artifact
 LIBTRACYCLIENT_JLL_NAME := LibTracyClient
-LIBTRACYCLIENT_JLL_VER := 0.9.1+1
+LIBTRACYCLIENT_JLL_VER := 0.9.1+2
 
 ## source build
 LIBTRACYCLIENT_VER := 0.9.1