streamline shuttle move/copy operations

[elfkuzco]

Rationale

This PR simplifies the file movement operation of the shuttle. It does this in the following way:

• keep one current location as the source of truth since all the book data (file) is the same across all current locations
• create the target locations using this first current location while simultaneously deleting any current location that isn't the original we are holding a reference to. Caveat is that book events are now showing as copies and not really as moves from one current location to another
• delete the original location and any other current locations that are left (especially if current location is greater than target locations)

This fixes #233

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.28%. Comparing base (53ad7cf) to head (c03fcce).
⚠️ Report is 10 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #274      +/-   ##
==========================================
- Coverage   81.39%   81.28%   -0.11%     
==========================================
  Files          55       55              
  Lines        2354     2362       +8     
  Branches      233      236       +3     
==========================================
+ Hits         1916     1920       +4     
- Misses        378      381       +3     
- Partials       60       61       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[benoit74]

• I realize it looks like we do not correctly handle the situation where a target location is same as a current one. Typical when we add a title to a second collection, we move from one current to the same target + another target. Or is this handled differently in terms of current/target locations?
• Deleted old location => Deleted book from

[elfkuzco]

I realize it looks like we do not correctly handle the situation where a target location is same as a current one. Typical when we add a title to a second collection, we move from one current to the same target + another target. Or is this handled differently in terms of current/target locations?

Nope, you are correct.

[benoit74]

LGTM