feat: add execution environment auto completion

[ganeshrn]

• Add support for execution environment (EE) configuration
  options received from client.
  Example client settings.json for EE options (default)

  {
   "ansible.executionEnvironment.enabled": false,
   "ansible.executionEnvironment.image": "quay.io/ansible/ansible-navigator-demo-ee:0.6.0",
   "ansible.executionEnvironment.containerEngine": "auto",
   "ansible.executionEnvironment.pullPolicy: "missing"
  }
  

• Add executionEnvironment service to handle initilization of EE
  and pulling plugins from within EE into cache path on local system

• In case EE is enabled update docsLibrary service to read plugin
  docs from local cache path after executionEnvironment service
  is initialized

• Add commandRunner utility to run command on local host or within
  EE based on settings passed from client

• Update ansibleConfig service to use commandRunner utility
  to run ansible-config and related commands

[tomaciazek]

Nice work abstracting away execution environment and brilliant caching mechanism!

I noticed that you're missing semicolons in many of the newly added lines. I'm not sure whether it was enforced by eslint, but Prettier was definitely configured to fill them in, it should be enough to install the Prettier extension and re-save the files.

Also, some inline and overview docstrings would be nice.

[ganeshrn]

/cc @yaegassy For review from coc.nvim extension perspective.

[priyamsahoo]

@ganeshrn, I don't think it's a great idea to use this.connection.window.showInformationMessage() or this.connection.window.showErrorMessage() in the language-server code base. I believe these are vscode APIs and we don't want to use them in the server code since server is meant to be used by other text editors and IDEs as well.

A similar issue is raised here: #15

[ganeshrn]

@tomaciazek Thanks for your detailed review. I have fixed most of them in my recent commit. Please re-review it.

I noticed that you're missing semicolons in many of the newly added lines. I'm not sure whether it was enforced by eslint, but Prettier was definitely configured to fill them in, it should be enough to install the Prettier extension and re-save the files.

Since I come from python world I tend to inherently ignore semicolons :-)
On a serious note your suggestion of using prettier extension worked like a charm.

[ganeshrn]

@priyamsahoo Based on the API documentation for the method it doesn't seem like it is specific to vscode.

    showErrorMessage(message: string): void;
    showErrorMessage<T extends MessageActionItem>(message: string, ...actions: T[]): Promise<T | undefined>;
    /**
     * Shows a warning message in the client's user interface. Depending on the client this might
     * be a modal dialog with a confirmation button or a notification in a notification center
     *
     * @param message The message to show.
     * @param actions Possible additional actions presented in the user interface. The selected action
     *  will be the value of the resolved promise
     */
    showWarningMessage(message: string): void;
    showWarningMessage<T extends MessageActionItem>(message: string, ...actions: T[]): Promise<T | undefined>;
    /**
     * Shows an information message in the client's user interface. Depending on the client this might
     * be a modal dialog with a confirmation button or a notification in a notification center
     *
     * @param message The message to show.
     * @param actions Possible additional actions presented in the user interface. The selected action
     *  will be the value of the resolved promise
     */
    showInformationMessage(message: string): void;
    showInformationMessage<T extends MessageActionItem>(message: string, ...actions: T[]): Promise<T | undefined>;

In any case the current test scope if for vscode extension. If in future we figure out it doesn't work with other clients we can fix it in appropriate way as part of Issue #15 for all the usages in the project including the messages added as part of this PR. IMO your comment is out of scope for this particular PR.

[tomaciazek]

We should avoid force-pushing once the branch is in PR review stage. For instance, I can't browse changes since my last review. Merge-commits are perfectly fine within branches - they are going to be squashed on merge to main anyway.

[tomaciazek]

Sorry, GitHub pulled a trick on me again and some replies to earlier comments ended up duplicated as standalone comments.

[ganeshrn]

@tomaciazek Fixed your another set of review comments. Some of them are still marked unresolved and I have provided my feedback on them. Please re-review the PR.

[ganeshrn]

We should avoid force-pushing once the branch is in PR review stage. For instance, I can't browse changes since my last review. Merge-commits are perfectly fine within branches - they are going to be squashed on merge to main anyway.

My bad. Something was not right in my local branch. Have fixed it now.

[priyamsahoo]

@priyamsahoo Based on the API documentation for the method it doesn't seem like it is specific to vscode.

    showErrorMessage(message: string): void;
    showErrorMessage<T extends MessageActionItem>(message: string, ...actions: T[]): Promise<T | undefined>;
    /**
     * Shows a warning message in the client's user interface. Depending on the client this might
     * be a modal dialog with a confirmation button or a notification in a notification center
     *
     * @param message The message to show.
     * @param actions Possible additional actions presented in the user interface. The selected action
     *  will be the value of the resolved promise
     */
    showWarningMessage(message: string): void;
    showWarningMessage<T extends MessageActionItem>(message: string, ...actions: T[]): Promise<T | undefined>;
    /**
     * Shows an information message in the client's user interface. Depending on the client this might
     * be a modal dialog with a confirmation button or a notification in a notification center
     *
     * @param message The message to show.
     * @param actions Possible additional actions presented in the user interface. The selected action
     *  will be the value of the resolved promise
     */
    showInformationMessage(message: string): void;
    showInformationMessage<T extends MessageActionItem>(message: string, ...actions: T[]): Promise<T | undefined>;

In any case the current test scope if for vscode extension. If in future we figure out it doesn't work with other clients we can fix it in appropriate way as part of Issue #15 for all the usages in the project including the messages added as part of this PR. IMO your comment is out of scope for this particular PR.

@ganeshrn, I think the API implementation belongs to https://github.com/microsoft/vscode/blob/9a21b53/src/vs/vscode.d.ts#L8848, which is specefic to vscode (I may be wrong).

But sure, if we see trouble executing this statement in other IDEs, we can have fixes for this in separate PR.

[priyamsahoo]

LGTM !

[tomaciazek]

Good job!

[ganeshrn]

Good job!

Thank you!