Refactor sandbox to its own Lua context and simplify security levels (Updater language 2)
Whole sandbox is complicated just because we need to ensure that configuration scripts can't access some advanced features. But that is some what questionable when it can install any arbitrary package with any arbitrary code in it. Yes true is that installation has to be optionally confirmed so we probably should have at least one protected level that denies access to uci, files and shell execution. But having more than two makes probably no sense.
Proposition is to have single Lua instance, separate from primary one. This instance is some what simple lua with possibility to switch to protected mode.
Also running sandbox in same instance as rest of the updater just complicates things and adds nothing of value. Yes we can share variables (by context magic) and functions but in the end there is no other reason. Just initializing new interpreter with specific limitations should be enough.
As part of this we should also implement: #198