Store database of information about what is currently linked

[SlyCedix]

Presently, it seems that tuckr uses the current structure of the dotfiles directory to determine what to remove upon using tuckr rm <group>. An issue arises when a group is changed structurally:

If one decides to relocate their bin group, for example, from $HOME/bin to $HOME/.local/bin. If the user did not run tuckr rm bin prior to making this change, tuckr has no way of knowing that there is even a link at $HOME/bin in the first place.

This is also an issue if a user deletes a file from the dotfiles without unlinking the group first as well.

This may work well as an addition #43, since the file tree could be serialized/deserialized with serde. This would also allow difference checking to notify the user if the current stucture matches or differs from the correct structure, perhaps with a tuckr fix <groups> command to remove orphaned links and create new links.

[RaphGL]

I'll leave this on the backburner for now and look at it after I'm done with the 0.11.0 milestone. I'm not entirely sure how to go about this either. Someone has suggested (#58) just watching the file system and then making the changes. Which is also a valid way to solve this ig (and potentially less work)

I personally am used to just removing and adding back again, so it doesn't really change much for me, but I'm willing to try and support the workflow in the future if it proves to be an actual problem for a lot of people.