Update 'clientVersion' in capture context request

I don't know if this is an issue for all merchants, but for the one I'm working on currently the capture contexts generated by the module are no longer valid if the 'clientVersion' is set to v2.0. They are valid if set to v2. They use semantic versioning, maybe specifying that older minor version errors now, they're on 2.4 currently. Patch attached.