[API] Extension ContentResolver / api to read/write card data

[ColgateTotal77]

Suggest to extend ContentResolver / api to read/write card data.

Can start from flag column, and then step by step add read/write for other columns.

[ColgateTotal77]

@criticalAY Hi, did you assign this issue to yourself because you are planning to work on this issue or because you will be mentoring user who will work on it? (I'm new here so not sure how everything works here)

[david-allison]

My comment from Discord: https://discord.com/channels/368267295601983490/701922522836369498/1519015288966742147

Rough thoughts:

CardContentProvider for the implementation - see how we do other modifications of entities

api/ for the 'nice' API:

• IMO: setFlagRaw(Int) and setFlag(Flag), where Flag is an enum
• API contributions must be LGPL

• ContentProviderTest - ensure you test forward-compatibility (flag: 8), fail a test if a backend update includes flag: 8, so we can update the Flag structure, and ensure invalid/negative values are handled

[ColgateTotal77]

About setFlag(Flag), if we will return number when getting flags from card, I don't think that user will use enum value to update flags. So setFlag(Flag) seems redundant.

[ColgateTotal77]

Also I see in CardContentProvider update we have NOTES_ID_CARDS and NOTES_ID_CARDS_ORD, what better use to update flag?