Workaround: fix #404 updating api for user data

[lipkau]

Description

workaround temporarily changed api routes to use version 2. This should be reverted to version latest as soon as a proper handling of how users work between cloud and on-premise is implemented

Motivation and Context

closes #404

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• [x] My code follows the code style of this project.
• [x] I have added Pester Tests that describe what my changes should do.
• [ ] I have updated the documentation accordingly.

[alexsuslin]

don't you think there will be much more issues with latest rather than certain number? I guess it should be exact api number by default and chaging it is a major change