Desktop,Mobile: Resolves #10073, #10080: Fix conflicts notebook doesn't work with the trash feature

[personalizedrefrigerator]

Summary

This pull request improves how conflicts are handled with the trash feature.

Fixes #10080 and #10073.

Notes

This PR does the following:

• Fixes a crash when displaying the conflicts folder.
• Fixes deleting items in the conflicts folder.
  • Previously, clicking "delete" would move an item to the trash, but it would still be visible in the conflicts folder. Additionally, clicking "restore" on such items did nothing.
• Fixes an issue where opening an item in the conflicts folder would throw a Missing property "deleted_time" exception.
  • This change also fixes Desktop: Resource links broken #10080.
• Refactors getConflictFolderId and getTrashFolderId into separate files to prevent a circular import issue.

When a conflict is deleted to trash, it now

1. Keeps the conflict as a conflict (is_conflict = 1)
2. Marks the conflict as deleted (deleted_time ≠ 0)
3. Shows the conflict in trash, but not in the "conflicts" folder

When a conflict is restored from trash, it is moved back to the conflicts folder.

Remaining issues

I've noticed the following remaining issues that could be addressed in a follow-up pull request:

• Currently, dragging a conflict note out of trash always moves it to "Conflicts".
• Editing a note in "Conflicts" causes the conflict note to disappear until another notebook is opened, then "Conflicts" is opened again.

Testing

To manually test this change,

1. Launch Joplin Server.
2. Connect to two different Joplin Server accounts.
3. Share a notebook from one account to the other.
4. Verify that it's still possible to open and edit a shared note.
5. Verify that it's still possible to delete and restore a shared note.
6. Create a conflict and verify that it can be deleted to trash.
7. Verify that a conflict can be restored from trash back to the conflicts notebook.
8. Verify that a conflict can be moved out of the conflicts notebook.

This has been tested successfully on Ubuntu 23.10.

On Android:

1. Create a conflict.
2. Verify that the application doesn't crash.
3. Delete a note from the conflicts notebook.
4. Verify that it is moved to the trash folder.

This has been tested successfully on Android 13.

[personalizedrefrigerator]

This check was moved from the top of the function to after needsShareReadOnlyChecks. This matches the behavior of the function prior to this commit.

This seems to be necessary to allow the new resource-related test to pass (see readOnly.test.ts).

[personalizedrefrigerator]

Marking as a draft until the test failures have been resolved (this should be done in the next few hours).

Edit: Fixed.