Multiple backend integration #103
Description
This issue describes integration with other backends and how to achieve it
How to deal with different id of backends? Some backends don't have a uuid and those who have may not have uuidv7... (like taskchampion)
Have the backends id as a task UDA, with stride.{backend-name} :: id:{backend-task-id},... (namespace.key :: value)
This allows checking what tasks have been mapped, and we can easily store other backend specific info.
Who is responsible for managing the format of the value?
It should be the backend's responsibility to version and manage the fields.
Example with taskchampion: stride.taskchampion :: id:{uuidv4}
In the case of git-backend it will store everything, so there shouldn't be a need to store the any UDA fields for it.