Make TeleNVDA's command gestures independent of NVDARemote

[cary-rowen]

Problem Description

TeleNVDA and RemoteNVDA share gesture settings. i.e.
[globalPlugins.remoteClient.GlobalPlugin]
This leads to a problem if the user is using TeleNVDA and changes some of TeleNVDA's gestures like script_sendKeys. If the user switches from TeleNVDA to NVDARemote, these gestures will still work in NVDARemote, especially script_sendKeys (NVDARemote does not support changing this gesture).

Although TeleNVDA is better than NVDARemote so people rarely fall back to NVDARemote. However we have to take this possibility into account for the user.

Possible difficulties

If you simply change the name of the function that defines the gesture to another name, it may cause problems:

1. The user's previous custom gesture settings will be lost in the new version.
2. NVDARemote's script sendKeys may have been modified and cannot be easily restored.

[jmdaweb]

Hi,
Fixing this issue is as easy as renaming the remoteClient folder to something different, such as TeleNVDA. However, the change may bring an advantage and a disadvantage for the users at the same time. Currently, switching from an add-on to the other keeps the same gestures, so they must be configured only once for both add-ons. In the other hand, some users may want different shortcuts for the two add-ons. Remember that NVDA Remote and TeleNVDA can't be running at the same time.
The gesture for sending keys is not a problem. NVDA Remote will always use f11. This gesture is handled without NVDA APIs. I'll keep this issue opened while I ask to the community.
Regards.