Remove camelCase renaming of field names

[jeremydrichardson]

Propose to remove the automatic camelCasing of field names when going through the transform pipeline.

We ran into issues where field names changed unexpectedly - but only on portal data. Tracked it down to this transformRelatedTables function that transforms the field names to camel case in the process.

I'm not opposed to having camel case as an option, otherwise is comes as an unexpected name transform.

Our application is we are manually mapping field names from FileMaker into our API using a JSON schema. In order to succeed we need to be able to predictably know what the FileMaker field name is so we can map it to our API field name. We ran into this issue only when we began using portals. It seems only the portal field names are being camel cased.

Let me know you thoughts on it and maybe some of the reasoning why you're camel casing in that step.