Allow to Specify Optional ScriptInterface VFS Jail

[smiley]

References and depends on #6472.

To clarify, while I am using the term jail, this would behave more like unveil.

Up to now, scripts are agnostic of other scripts and have no control over what gets loaded. However, with ES Modules being included with #6472, it presents a potential problem if all of the VFS is visible to a script as it might lead to undesirable connections forming over time intentionally, or unintentionally if a map script is able to use a script in gui/ for example.

An edge case is globalscripts which would need to be loaded regardless. However, for the existing non module code, its not a problem as the scripts would loaded in as they always have been. For modules, globalscripts itself would be exposed as a built-in module in the runtime. import { Vector2D } from "Pyrogenesis";. This same pattern could be used to expose internal variables and functions to modules.