apply reserved keywords mapping

[o-mishch]

Fixes #2
This PR is ready for review.

Risk
This PR makes no API changes.

Testing Plan
Verify test app connectivity and that all unit tests pass.

Summary
avoid using keywords when generating RPC definitions.

CLA

• I have signed the CLA and this pull request adheres to the Contributing Guide.

[o-mishch]

@mrapitis, @nickschwab please review this PR

[theresalech]

@mrapitis please let us know once you've reviewed. Then @crokita will start his review. Thanks!

[mrapitis]

@theresalech Ford has reviewed and approved this PR.

[crokita]

This is the feedback I have so far for when using the generator.

Capitalization overriding rules should only apply to the class names, and not to the enumerated values or to the methods that access them. See the following enums whose getter method names get capitalized:
- ImageFieldName
- MetadataType
- TextFieldName
- MessageType

I noticed some inconsistencies in application of the method name changes. Some also have changed the static key values to include PARAM (ex. VehicleDataResult's getResultCodeParam uses KEY_RESULT_CODE_PARAM, but in TouchEvent for getIdParam the key doesn't change. This isn't the only case).

[crokita]

Review is finished. See comment from earlier in the conversation. @o-mishch

[o-mishch]

@crokita In RESERVED_KEYWORDS there are keywords KEY_RESULT_CODE and getResultCode, that’s why it was replaced appropriately in VehicleDataResult.
as well there is keyword id, but there wasn’t keyword KEY_ID, then’s why was changed only getidParam in TouchEvent

[crokita]

Thanks for the clarification. The last part of my post can be ignored, then.

[o-mishch]

@crokita issue with capitalisation of enum getters resolved in 13e04ed

[crokita]

Tested the changes and things look good. I'm going to change the base to our release branch since we have a release candidate ready for review and revisions.