Nodes who are not currently master do not update the ElectMasterService when dynamically setting min_master_nodes

When updating the min_master_nodes setting via the Cluster Settings API, the change is propagated to all nodes. The current master node also updates the ElectMasterService and validates that is still sees enough master eligible nodes and that it's election is still valid. Other master eligible nodes do not go through this validation (good) but also didn't update the ElectMasterService with the new settings. The result is that if the current master goes away, the next election will not be done with the latest setting.

Note - min_master_node set in the elasticsearch.yml file are processed correctly

Closes #5494
Fix incorrect return impl in SmileXContent.createParser.

Close #5510
Use build-in function to write field name in JsonXContentGenerator#writeRawField

The #writeRawField method forcefully writes a `,` spearator expecting a raw field
to never start as the first value in an object.

Closes #5514
Revert "Use build-in function to write field name in JsonXContentGenerator#writeRawField"

This reverts commit 674373015dd88768847e7ee525e9411da446ffbc.
release [1.0.2]
Bumped version to 1.0.3-SNAP & added version 0.90.14