Fix Edge Case Running Status of Sandbox

[IntegerLimit]

This PR fixes edge cases where the running status of the GroovyScript sandbox is reported, falsely, as not running.

Reproduction Case:

import gregtech.integration.groovy.GroovyScriptModule
import net.minecraft.item.ItemStack

println('Hello World!')

println(GroovyScriptModule.isCurrentlyRunning())

var test = { ItemStack stack ->
    println("Hello World (2)! " + stack.toString())
}

test(item('minecraft:apple'))

println(GroovyScriptModule.isCurrentlyRunning())

This script uses GT just to report the status of the sandbox, but it should work without gt dependency. This was reproduced in an instance with just GroovyScript and its deps, + GT and its deps.

Output of running the above script:

[21:59:45] [SERVER/INFO] [groovyscript]: ========== Reloading Groovy scripts ==========
[21:59:45] [SERVER/INFO] [placeholdername]: Running scripts in loader 'postInit'
[21:59:45] [SERVER/INFO] [placeholdername]:  - running main
Hello World!
true
Hello World (2)! 1xitem.apple@0
false

[Wizzerinus]

I think that,

[brachy84]

Wtf? How does that fix your issue?

[IntegerLimit]

Fixing review comment now. I believe the fix still works with the proper fix, but will recheck.

[brachy84]

Its closures... When they stop running is always set to false

[IntegerLimit]

Its closures... When they stop running is always set to false

Breaks for closures... in scripts themselves, outside of event handlers, etc.

[IntegerLimit]

Fix tested, works as intended.

[IntegerLimit]

Essentially, here's why I think this issue occurs:
Closures running inside scripts still have that runClosure method called to run them.
When the closure finishes, running is set to false, therefore breaking the status.

Closures running in scripts are... pretty common.