TODOs from #48

[wavefunction91]

• [ ] Check integration of Logger into ResourceSet once initialization is set up properly
• [ ] Design and deploy default initialization strategy for Logger instances within RuntimeView

[ryanmrichard]

Some TODOs pertaining to loggers I came across from my work on #50. I think this batch falls under he first bullet, but wanted to be more specific since it's been a while.

• [ ] Check const-ness of progress_logger/debug_logger (currently not possible to call from a const ResourceSet; maybe that's intended, but it surprised me).
• [ ] Test ResourceSet that actually has loggers
• [ ] Add logger comparison to ResourceSetPIMPL
• [ ] Test ResourceSet/ResourceSetPIMPL comparisons, cognizant of loggers
• [ ] Test ResourceSet/ResourceSetPIMPL methods for getting/setting loggers
• [ ] Make ResourceSet::empty check loggers
• [ ] Right now the loggers in ResourceSetPIMPL are stored as pointers; this makes them behave differently than all other state. Not sure if the special treatment is warranted or not.

[ryanmrichard]

Same idea, but expanding on the second bullet this time.

• [ ] document/test progress_logger/debug_logger in RuntimeViewPIMPL
• [ ] test set_progress_logger/set_debug_logger in RuntimeView
• [ ] Properly account for the logger in operator==

While not part of either of the original bullet points we also need some sort of design documentation and tutorials/high-level user documentation.