URigVMBlueprint::CompileLog can spam the editor log when verbosity is set to Log

It seems that URigVMBlueprint::CompileLog is spamming the log whenever a call to BP_SCOPED_COMPILER_EVENT_STAT, including for blueprints that are unrelated to control rig.  The log messages are only visible when the global log verbosity level has been set to Log.

A workaround is to pass false to the FCompilerResultsLog constructor however, doing that seems to result in messages from the control rig logger not being output to the log window.

• Open the DefaultEngine.ini file for whatever project you want to repro in (eg. Samples\Games\Lyra\Config\DefaultEngine.ini)
• In the [Core.Log] section add global=log. 
  • If [Core.Log] doesn't exist, add it.
• Open the project and compile a blueprint that doesn't reference control rig
• Open the log window and you'll see messages from the control rig log that look like:
  • LogBlueprint: [AssetLog] /Script/RigVMDeveloper.Default_RigVMBlueprint: [Compiler] [3722.91] Compile of Default_RigVMBlueprint successful! [in 0 ms]