Adds option to force update same task mentions in current file

[nkakouros]

This tries to fix the case when multiple viewports list the same task. Updating the task in one of them and saving can have the unwanted result that the changes get reverted as taskwiki uses non-updated mentions of the task as authoritative.

For example:

# Viewport 1 | project:parent
* [ ] My task

# Viewport 2 | project:parent.child
* [X] My task

# Viewport 3 | +label
* [ ] My task

In this scenario, where the second occurrence of the task has been marked as complete (with the TaskWikiDone command), if the user saves the file, the task will be marked as pending. Common change logs for such tasks look like:

2022-01-31 09:46:27 End set to '2022-01-31 09:46:27'.
                    Status changed from 'pending' to 'completed'.
2022-01-31 09:47:24 End deleted.
                    Status changed from 'completed' to 'pending'.
2022-02-01 10:34:55 End set to '2022-02-01 10:34:55'.
                    Status changed from 'pending' to 'completed'.
2022-02-01 11:16:33 End deleted.
                    Status changed from 'completed' to 'pending'.
2022-02-01 11:17:43 End set to '2022-02-01 11:17:43'.
                    Status changed from 'pending' to 'completed'.
2022-02-01 15:30:37 End deleted.
                    Status changed from 'completed' to 'pending'.
2022-02-02 10:47:29 End set to '2022-02-02 10:47:29'.
                    Status changed from 'pending' to 'completed'.
2022-02-02 10:47:33 End deleted.
                    Status changed from 'completed' to 'pending'.
2022-02-02 10:49:42 End set to '2022-02-02 10:49:42'.
                    Status changed from 'pending' to 'completed'.
2022-02-02 10:49:53 End changed from '2022-02-02 10:49:42' to '2022-02-02 10:49:52'.

bouncing between pending and completed. This happens for other task attributes as well (e.g. due time).

PS: I would really like to write tests for any pending PR I have and have them merged, but I can't get the test suite to work.

Edit: I now see that #222 deals with the same issue. Feel free to close this if the older PR makes more sense.

[liskin]

PS: I would really like to write tests for any pending PR I have and have them merged, but I can't get the test suite to work.

I've been trying to get to this but life keeps interfering. :-/
If you'd like to try and hack on this together, this may nudge me to get to it earlier. Reach out via IRC or Gitter (or Discord, although I only read that piece of crap once a day or two) then.

Edit: I now see that #222 deals with the same issue. Feel free to close this if the older PR makes more sense.

Your implementation seems more robust though. #222 looks like it may discard some unsaved changes in the buffer.

[litwol]

What remains for this to be merged?

[liskin]

What remains for this to be merged?

The CI needs some tender loving care, so the existing tests are failing and thus nobody even bothered to write tests for this new functionality. And then all the maintainers are burnt out and/or having different priorities in life.