Casing is inconsistent between property definitions in schemas and property names in element props

[ColinKerr]

iTwin.js forces the first letter off every property to lower case when generating the element props. This is confusing because the standard for schema definitions is to start with an upper case. So the schema and the json are always inconsistent.

e.g.

EC Property Name	JSON Property Name
Additional_Information	additional_Information
Agents_Record_Number	agents_Record_Number
Area_Region	area_Region
MyCustomProperty	myCustomProperty
GPSCoordinateValue	gpsCoordinateValue
PIPELINE_NUMBER	pIPELINE_NUMBER

[rschili]

Mentioning ECJsNames.toJsName() here, which bridges the two naming schemes for now, but agreed that it's still confusing.