Monkey-patching browser APIs with ZeroFrame

ZeroFrame currently monkey-patches AJAX browser APIs to add AJAX key. It would also be good to monkey-patch some other browser APIs, like `localStorage` or `history`, to call ZeroFrame's wrapper actions instead of directly browser APIs. This would make it possible to use some third-party libraries (like JS routers which use History API, maybe some storage helpers) with ZeroNet without any modifications to them (this currently requires to modify them to use ZeroFrame instead of browser APIs).

Some of APIs which should be monkey-patched are:

* `localStorage`: Use wrapper's `wrapperGetLocalStorage` and `wrapperSetLocalStorage`. However, I don't know if this is possible because browsers prevent accessing and modifying `localStorage` object in iframe sandbox.

* `History`: Use `wrapperGetState`, `wrapperPushState`, `wrapperReplaceState` and correctly handle URL rewrites in other `History`'s objects. This would be easier because you can access them inside sandbox, but they just don't do anything.

* As well as some other wrapper actions like `wrapperOpenWindow` and `wrapperSetTitle`.

从现有的 AJAX 浏览器 API monkey-patching 入手，追踪 ZeroFrame wrapper 操作的调用方式。评估拦截 localStorage 和 History 的可行性，包括 URL 重写，然后考虑 wrapperOpenWindow 和 wrapperSetTitle；完成的标准是受支持的第三方库无需进行 ZeroNet 特定的修改即可使用这些 API。

由索引模型根据 Issue 内容生成。