Diagnostics when saving

When saving a model, hyperstack follows the relationship tree and also saves all associated models that have changed.

This is proper behavior, but in a large system it may lead to having records being saved that you might not expect.

It would help if during the save we dumped a picture to the JS console of what the tree looks like, so you can see why certain models get saved.

No file or test is named. Trace the model save entry point and the relationship-tree traversal described in the issue, then identify existing console or diagnostic conventions. Done means saving a model can show the associated models and relationships that caused additional saves in the JavaScript console.

Written by the indexing model from the issue text.