Fix issues with extension sync

[auxves]

Short description of what this resolves:

This PR fixes issues that prevented extensions from being synced properly.

Changes proposed in this pull request:

• Properly throw an error when one occurs
• Scan for missing extensions correctly

Checklist:

• I have read the contribution guidelines.

[shanalikhan]

We need to sync the map function by using async/await in the following line.
https://github.com/shanalikhan/code-settings-sync/blob/v3.3.0/src/service/pluginService.ts#L225

Can you improve this and send me PR.
Delete extension seems to working fine, i will test more.

The current output:

[x] - EXTENSION: beautify - INSTALLING

[x] - EXTENSION: debugger-for-chrome - INSTALLING

[x] - EXTENSION: team - INSTALLING
    - EXTENSION: debugger-for-chrome - INSTALLED.
      1 OF 3 INSTALLED

    - EXTENSION: team - INSTALLED.
      2 OF 3 INSTALLED

    - EXTENSION: beautify - INSTALLED.
      3 OF 3 INSTALLED

``

[auxves]

@shanalikhan The problem with syncing the two is that Promise.all executes the installations in parallel. The only way I could think of to resolve this would be to use blocking code, which is not recommended for a VSCode extension because it can freeze the extension host. What I suggest we do is just remove the log stating that an extension is installing and only leaving the one that says that it was installed. What do you think?

[shanalikhan]

just remove the log stating that an extension is installing

For the user point of view, we must show which extension is installing and installed completely.

it can freeze the extension host

Yes , we should not use that.
What about we can use simple for loop instead of map and other stuff. Explore other ways.
You can look into the previous code in master branch, how in CLI i'm holding the next installation CLI command that waits for previous command to complete.

But we need to show what is going to install and what has been installed.

[auxves]

What about we can use simple for loop instead of map and other stuff.

That is an example of blocking code. For loops prevent other code from running until it is finished, and extension installation takes a long time.

Edit: I guess we will have to use for loops after all. I couldn't find a suitable replacement.

[auxves]

@shanalikhan Here's a PR that will sync the INSTALLING and INSTALLED messages: #910