Windows runtime settings + shared libraries

[jrmadsen]

• Following Use GetProcessIoCounters on windows for get_bytes written and read #169, google test has been re-enabled for Windows and a few tim::settings are being noted as not working in some places for an unknown reason.
• This appears to be relatively isolated to only a couple settings not being "respected" properly. I.e. they are set but ignored for some reason.
• For now, the testing is going to ignore these issues in order to get Use GetProcessIoCounters on windows for get_bytes written and read #169 merged
• Known settings issues
  • when usingtim::settings::push<...>(), tim::settings::instance<...>() access method still refers to the original settings. Work-around: use the settings instance returned from push<...>()
  • runtime tim::settings::flat_profile() and tim::settings::timeline_profile() values are not respected when pushing/popping to storage. Work-around: using quirks (i.e. encoding flat/timeline at compile-time) works fine.

[jrmadsen]

@pwm1234-sri I suspect these issues are possibly related to Windows weird shared library linking, e.g. somehow these settings are referenced in an intermediate library and changing them in the exe updates a different set of symbols instantiated in the exe binary.