fix: document tracking issue when path of document changed

[huddeldaddel]

Proposed Changes

This change removes the tracking of documents being renamed via document.onDidRename.
It seems that is actually not required (anymore) since the previous document gets removed and then added again. I check that for all use cases I could identify:

• Creating a new file / saving it
• Opening a file / saving to different location

Closes #176

Checklist

To ensure you provided everything we need to look at your PR:

• Brief textual description of the changes present
• Visual demo attached
• Steps to try out present, i.e. using the @bpmn-io/sr tool
• Related issue linked via Closes {LINK_TO_ISSUE} or Related to {LINK_TO_ISSUE}

[CLAassistant]

All committers have signed the CLA.

[huddeldaddel]

So far I was not able to come up with a unit test that can save a document. Saving the current document to a new destination would be part of the required user interaction to test for this change. The available commands (that I found) do not accept a URL destination - instead they require user interaction via file dialog.

[barmac]

Thanks for the PR. Perhaps if the change cannot be tested via API, we will manually confirm the fix.

[barmac]

In the meantime, please adjust the commit message to adhere to conventional commits: https://www.conventionalcommits.org/
We use that for semantic releases.

[barmac]

It works fine in manual tests. Let's try this out.

[barmac]

I noticed you updated the PR title but not the commit message. I will do that in the merge.