fix: Correct spelling and semantic mistakes in method naming

[fishey2]

Change list

• corrects spelling and semantic errors
  • SupportsCustomSslCertOption method setCustomSSLCert() is now getCustomSSLCert() affects XCUITestOptions
  • SupportsSimulatorTracePointerOption method doesSimulatorTracePointerd() is now doesSimulatorTracePointer() affects XCUITestOption
  • SupportsShowChromedriverLogOption methods setDhowChromedriverLog(boolean) and doesDhowChromedriverLog() are now setShowChromedriverLog(boolean) and doesShowChromedriverLog() respectively affects ExpressoOptions and UIAutomator2Options

Types of changes

What types of changes are you proposing/introducing to Java client?
Put an x in the boxes that apply

• No changes in production code.
• Bugfix (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 not work as expected)

Details

No functional changes

[linux-foundation-easycla]

• ❌ The email address for the commit (7d28b26) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[mykola-mokhnach]

Could you please sign CLA?

[fishey2]

I should have now signed the CLA

[mykola-mokhnach]

In order to not make this change breaking it would make sence to mark method names containing typos as @Deprecated and keep them for now along with corrected ones. We could remove deprecated methods in later releases.

[fishey2]

The changes should reflect your suggestion now @mykola-mokhnach: Deprecated rather than remove methods containing typos.

[valfirst]

@fishey2 would you mind fixing Checkstyle violations?

[fishey2]

@valfirst happy to work around the Checkstyle issue, however the actual checkstyle issue is apparent because it thinks the deprecated method setCustomSSLCert() overloads setCustomSSLCert(String) instead of getCustomSSLCert(), which should have been the case.

In this case there is only the two methods in the class and moving it up shouldn't affect anything else, but workaround the checkstyle issue. I will push this change now.