[Standing ticket] Verbose diagnostics to support advanced debugging

[SebastianMC]

With increased frequency of breaking changes introduced by Obsidian (1.5.4, 1.6.0, 1.6.3) the effort to catch up, investigate and fix the plugin increases. This ticket (its branch actually) will contain rich debugging support (including tons of console.log statements) to allow quick diagnostics of any future breaking changes of Obsidian.

Breaking change in Obsidian 1.5.4 - I treated as incidental, and all the debugging support (configs, console.logs, etc.)
was 'discarded after use'.

Breaking change in Obsidian 1.6.0 - I wished I would have kept all of the debugging support mentioned above....

Breaking change in Obsidian 1.6.3 - it looks that breaking changes become rather a rule than exception, so the rich diagnostics and debugging support should remain at hand.

The one to start with is #147 - some not-yet-investigated breaking change of Obsidian 1.6.3 causing minor inconvenience