Add syntax for dynamic loops

[AdvancedAntiSkid]

Is your feature request related to a problem? Please describe.
HSL is trying to be a real programming language, however housing has too many limits for this. Recently I've found a workaround to implement loops via recursive function calls.

Describe the solution you'd like
Create fully-functional for and while loops. Lets take a look at how a for look should look like.

Users should declare something like this:

fn foo() {
    for (stat player i = 0; i < 10; i++) {
        chat($"iter: {i}")
    }
    chat("something after loop")
}

This should be converted to housing-compliant functions:

fn loopInit() {
    stat player i: int = 0
}

fn loopTick() {
    stat player i: int

    if (i < 10) {
        chat($"iter: {i}")
        i++
        loopTick()
    } else {
        loopMerge()
    }
}

fn loopMerge() {
    chat("something after loop")
}

Describe alternatives you've considered

Additional context
The merge step must be added to capture the remaining code after a loop. According to my testings, the actions after a (recursive?) function trigger DO NOT wait for the function to complete. Meaning that we can corrupt logic flow if we have any code with dependency to the loop after the loop. This forces us to put the remaining code in a merge function that is invoked after the loop is completed.

[AdvancedAntiSkid]

Because of Hypixel's function call spam check, we must sleep for few ticks before we recursively call the tick function. This is sadly somewhat unpredictable; so move code to the merge block if and only if the following code could potentially modify the state within the loop's body. Also do some research on how much should we wait before recursive call to make sure Hypixel does not block the call. I'm also interested in the maximum call stack depth - how much recursive calls are permitted.

[AdvancedAntiSkid]

Eventually also need to make loop nodes implement Executable, to let metaprogrammers use loops as well.

[AdvancedAntiSkid]

Due to the Housing runtime's limitations, you need to insert at least sleep(5s) between each iteration. Otherwise it is very likely that the runtime will ratelimit the call stack and exit the loop.

[AdvancedAntiSkid]

Based on the response of ConnorLinfoot, in this Hypixel thread, function triggers are essentially "non-blocking" calls, meaning the following actions will not wait for the previous function to complete. Because of this, we need to make sure that all code below the loop are encapsulated in a merge function, that is invoked by the loop's tick function if no more steps are left to complete.

[AdvancedAntiSkid]

Decide what to do with pauses, as currently if I wanted to do custom pauses between iterations, I would end up with to separate pause actions: one generated by the compiler, another one defined by me