Very rudimentary "tests"

These are in no way sufficient to verify the expected behaviors of the
library. This simply exists for initial debugging during development.
Model and collection proxying via hasOne/Many

These implementations do not yet fire off any request to load data, but
they do return their appropriate model or collections. Other behavior
that should be implemented is the ability to define nullable attributes
as well as aliasing attributes as different names for the sake of
proxying (e.g. model.foo_id gets aliased as model.foo proxy).