Further robustness for putClientSettings

[matthewblain]

Summary

Increase robustness in corner cases possibly encountered by putClientSettings

Follow-on to issue #1524

Inconsistent results should be highly unlikley now, as the entire client configuration is passed to the server. In the typical UI flow there will be an update which should write the correct value.

Robustness improvments could include:

Add a transaction to the server so an error will be reported on 'collision.'
Have the client retry on error somehow. Perhaps by recording a timestamp for last client side update and last server side sync, and occasionally validating that the two match.
Have the client report errors, e.g. add an event to who_service like widget.analytics.logEvent(name: 'WhoServicePutClientSettings', parameters: {'result': response.statusCode});

Reproduction Steps

Somehow rapidly make client changes using a slow server.
Result: Possibly something other than the last setting will be the perised one.

Expected Behavior

Simultaneous requests will error out in some reasonable fashion.

System

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• App Version: [1.2.0+14]

Additional Context

Add any other context about the problem here.

Screenshots

Screenshots

Add any relevant screenshots here

Checklist:

• Searched the existing issues to ensure you are not creating a duplicate.
• Followed the Contributor Guidelines.

[stale]

This item has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.