Support setting ContactsContract.DataColumns.IS_READ_ONLY when inserting any NewDataEntity (e.g. name, email, phone, etc)

[vestrel00]

Problem

As discussed in #301, there is currently no way to specify the value of ContactsContract.DataColumns.IS_READ_ONLY when inserting data rows using the insert APIs provided in this library.

Solution

Add isReadOnly property to NewDataEntity interface and incorporate it when inserting new data rows.

Note that including the IS_READ_ONLY column in the projection array of queries result in an exception being thrown. This means that we are unable to read the value of it and in turn we are unable to add the isReadOnly property to the more generalized DataEntity. However, it is possible to refer to the column in selection/WHERE clause of queries. We can at least provide an extension function to check its value; #307

• Create public Fields.DataIsReadOnly, which should be added to Fields.All list but should NOT be included in the final projection array passed to any query APIs!
• Check that Fields.DataIsReadOnly can be used in WHERE clauses of query and delete APIs
• Add extension function to NewRawContact that sets the read-only property of all data in it.
• Update relevant in-code documentation.
• Document the side-effects of setting this to true and that it should not really be used in general application use cases.
• Update relevant docs (about-api-entities.md)
• Update gh-page branch
• Close NewCustomDataEntity implementations now require additional property isReadOnly #311

[vestrel00]

🔥 🔥 🔥 🔥 🔥 🔥 🔥 🔥
This is now release in 0.3.1!
🔥 🔥 🔥 🔥 🔥 🔥 🔥 🔥