Implement a timeout as a fail-safe for long running practices

There are some cases where students will write code that produces effectively infinite loops. and we can wrap around those and break out of those by limiting the of time a practice might be running total.

We may not detect the infinite loop but at least we can add that as a way for students to not lock the current tab in their browser and raise information that, not only did the result not work, but also maybe there's an infinite loop in the student's code and provide an error explanation + a link to the GDLibrary or something for a write-up on that.

See #960 for example. implementing this feature would fix that issue