Decoupling SPARK_WLAN_Loop() from the user loop()

[BDub]

@bkize

To at least partially address some of the concerns above, is it possible to only do the WiFi loop if the user code is already executing a delay call? In other words, if the user code isn't doing anything but waiting for the next 100ms or longer, then allow the system code to do a WiFi loop. I think this should be the default behavior.

You and I think alike I suggested that here:

Delay killing core

On a high level, Interrupting every 50ms to run a 5-6ms background task will also add randomly 5-6ms delays in your user code, unless you wrap sensitive code with __disable_irq(); and __enable_irq();