feature: add flag for cloud providers to say whether they support the /sessions endpoint, to avoid making calls that we know won't work

[KritikaSahare1611]

Appium or Appium Desktop?

You are reporting an issue at the Appium Desktop repository. Appium Desktop is a wrapper around Appium. If you are having trouble running tests, it is much more likely that the problem you are encountering is not a problem with Appium Desktop but with Appium. For that reason we require you to have tried your testcase with Appium CLI before reporting issues. Check the checkbox below to confirm that you have proven your issue does not reproduce on Appium itself:

• I have verified that my issue does not occur with Appium and should be investigated as an Appium Desktop issue

The problem

Not able to attach to the session as Attach to session dropdown is showing blank.

Environment

• I am running Appium Desktop version <1.22.0>.
• I am on (Windows):

[KazuCocoa]

Currently, this behavior is expected since the current implementation depends on the response of /sessions API.
It needs to implement copy&paste session-id and attach to it.

[jlipps]

@KazuCocoa maybe we should have an internal config option for servers, such that if we know a server doesn't support it, we show a "Not supported" card instead of showing the UI. Then if a server eventually supports /session they can open a PR to update their config.