Building block request: expose refactor log in parsable format.

Please select if your request is either something new or an enhancement

[ ] Enhancement of an existing Feature.
[x] Request of a new feature.

Please select the area your request applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[x] Workspace - VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup - Dendron's Lookup Command
[ ] Views - Dendron Preview, Tree View, Side Panels in the UI
[ ] Schema - Dendron Schemas
[ ] Pod - Data import from / export to Dendron
[ ] Publish - External Site Publish
[ ] Markdown - Markdown features, such as syntax support and features

Is your feature request related to a problem? Please describe

This is a building block feature request there are two main use cases that this building block can be applied to:

1: Allow refactors to be picked up from another vault. Example let's say there is a central vault (team shared vault) and there are personal vaults that link into team shared vault. All team members have access to the shared vault, but each only has access to their personal vault. Now if someone does a refactor in the central vault the other links will break. (A work around is to checkout the central vault reset back to how things were and reply the refactors again from the central vault). However, would be way nicer experience if personal vaults could piggy back on top of the central vault and "suck" in all the refactors that were performed on the central vault.
2: This one is actually what prompted to write this feature request: is to allow other apps to automatically detect changes of refactors that happened in Dendron. Use case: using something like yED to do diagramming and then link into Dendron from yED diagrams. yED saves its data in graphml and has description field that can be attached to each node, hence each node can have a link into Dendron. Then if Dendron is refactored I would like all the links to still be alive within yED which for now can be done through careful gatekeeping of refactors, but with the refactor log can be automated for external app like yED to pick up the changes.

Describe the solution you'd like

Refactor log in JSON format such as

{"action":"rename"/"refactor-hierarchy", "oldValue":"", "newValue":""}

Describe alternatives you've considered

TBH just realized tonight that yED can be integrated so well with Dendron (given that it has description field and saves data in refactorable format graphml) and being careful with refactors, first doing refactors in Dendron and then running some scripts that would run over graphml to adjust the links even without this building block.

Additional context

Thought would still be good to share this idea of integrating Dendron with a tool that specializes in Visualization by linking from yED into Dendron (can creates system diagrams & mind maps in yED and use Dendron as a query tool).

dendronhq / dendron