Automatically stop and resume execution before hitting maxCommandChainLength

[Adrodoc]

When debugging large datapacks it can happen that more than maxCommandChainLength commands are executed. This is really bad as it leaves the debugger in an undefined state.
Instead of requiring the user to stop the debugging session and increase the limit with /gamerule maxCommandChainLength 2147483647 we could query the value with

execute store result score maxCommandChainLength -ns-_global run gamerule maxCommandChainLength

and stop early before reaching that limit as if we would hit a breakpoint (but ideally with a different message) and immediately schedule resumption.