fix appium version to latest

[eyaly]

One-line summary

Issue : #1234 (only if appropriate)

Description

A few sentences describing the overall goals of the pull request's
commits.

Types of Changes

What types of changes does your code introduce? Keep the ones that apply:

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Configuration change
• Refactor/improvements
• Documentation / non-code

Tasks

List of tasks you will do to complete the PR

• Created Task 1
• Created Task 2
• To-do Task 3

Review

List of tasks the reviewer must do to review the PR

• Tests
• Documentation
• CHANGELOG

Deployment Notes

These should highlight any db migrations, feature toggles, etc.

[kb-kerem]

Hey @eyaly, I think fixing the appium version to latest in the example might be problematic when there are breaking changes. @FriggaHel @konraddysput what would be your take in this case?

[eyaly]

Thanks @kb-kerem . But we can't leave it as 2.0.0 because it is not a supported version.

[kb-kerem]

Thanks for the heads up @eyaly. Looking at the platform configurator examples (https://app.saucelabs.com/platform-configurator) for ios and android real devices, latest seems to be the way to go. I'll merge it as is 👍