support @adobe/aio-lib-state and @adobe/aio-lib-files

If we support #32, we can have a custom require loader, that will load our custom implementations of:
1. @adobe/aio-lib-state
2. @adobe/aio-lib-files

These will support all the APIs available.

1. @adobe/aio-lib-state - in memory hashmap, backed up by a .json file written to disk, and read on startup.
2. @adobe/aio-lib-files - in memory file tree, pointing to a specific location on disk as the root to read the files from. The file hierarchy is read on startup

Start by reading issue #32, then review the requirements for @adobe/aio-lib-state and @adobe/aio-lib-files described here. Done means a custom require loader provides implementations of both packages, including their available APIs, with state persisted through a JSON file and files rooted at a disk location.

Written by the indexing model from the issue text.