Populate both next_token and nextToken.

Fixes #1968.

This bug was introduced due to an issue with how boto handled the nextToken
field in responses, which meant that it was exposed with the incorrect
name. The fix caused existing code to break, so now both versions are made
available. New code should use next_token.

@toastdriven, please review.