Chore: Drag and drop fixes, CRDT preparation, I18N message store refactor, etc. (#51, #60, #67, #74, #75, #80, #87, #88, 91)

[dev-guy]

Please Select Squash and Merge

Changes

• Implement Odd drag-drop behavior with one card and two columns #51, Refactor for CRDT-based multiuser support #60, Convert Lang.js to typescript #67, Dragging a card within a column doesn't display a drop shadow #74, Rename $columns[].slots and Column prop 'slots' to 'cards' #75, Add $stores alias #80, Relative import paths need explicit file extensions in EcmaScript imports when '--moduleResolution' is NodeNext #87, Dragging a card to a column updates the column's card count, but it isn't decremented #88, Add column and card indices to cardRemove event data #91
• Change version to 1.1.0
• Update dependencies

Checklist

• I imported the Kanban component based on this branch into another app and tested all features to the best of my ability

Notes

#60 - This additional PR expands on this PR to add CRDT-based multiuser functionality to svelte-kanban.

#74 - Dragging a card within a column behaves the same as dragging it into a different column. The behavior might feel a little clunky and unexpected because the dragged card is rendered as an empty rectangle so the user can tell where the card will return to if they drop the card off the board (in other words: cancel the drag and drop operation). To drag a card down, you have to drag it a long way! I prototyped alternative UX's but the code was complicated and I eventually decided that it was bad UX for drag-across versus drag-within to behave differently (as it did before this PR) - at least I couldn't come up with a good enough reason. After all, that's why I created #74 in the first place. The existing behavior is semi-unpredictable.

Screenshare.-.2023-09-19.2_12_26.PM.mp4