Improve ORM documentation

[kilnerm]

The ORM documentation needs reviewing and updating to make it a little more comprehensive.

This issue is raised to track the update.

[kilnerm]

Feedback from Slack:

Also one thing that tripped me up was case sensitivity of it all, I had a property in my model with upper case like appId, and I could’t fetch from database due to a cryptic 702 error, something about codable and appId, until I googled and found something about case sensitivity. So now I added CodingKeys to handle the case like appId = “app_id” and then need to use app_id in the query as well. I don’t know if my solution of overriding the CodingKeys is the best, maybe there is a correct way of handling it? If you are going to look into the documentation I would suggest to mention how to handle variable names that contain upper case, it would be useful for future noobs (such as myself) faced with fetching error first thing out of the box, and remove some frustration

[kilnerm]

The update should include some sample code that demonstrates how to use predefined tables (created using Kuery or direct on the DB) with the ORM.

[kilnerm]

Add better examples of using QueryParams