Resource versions tracking

[kirillt]

Related to #27

Every time a resource has changed, we can represent this change as a transition from id1 to id2. This transition we can store in replicated state (or send to another app instance, but it will complicate implementation and should be avoided if possible). Afterwards, it should ease conflicts resolution.

[kirillt]

When we'll have version storage, we should update it with new versions in this spot:

ARK-Navigator/app/src/main/java/space/taran/arknavigator/ui/fragments/GalleryFragment.kt

Line 81 in 583c1f9

Log.d(GALLERY_SCREEN, "RESULT_SAVE_URI: $saveFileUri")

We'll also need to implement either propagation of user-defined metadata (tags, scores, properties) from older versions onto newer versions.

[kirillt]

Attached bounty: https://gitcoin.co/issue/29635

[Sixto5]

Hey @kirillt

Thank you for sharing this project!

I'm reaching out to share our invitation to support your issue via OpenQ marketplace. We are permissionless and free, see more here: https://www.openq.dev/

Zero hassle from your side 🙂 We will mirror your bounty, adding the same budget.Devs from our community might solve your issue. So then we can support you meanwhile our marketplace grows.

If you give me your thumbs up we will do it and share the link again here to you for full transparency!