Update mops and call `mops sources` with `--no-install` flag

[ZenVoich]

Sometimes errors may occur when a user runsmops install because ext calls mops sources which starts with mops install, so we get two concurrent install processes. With --no-install flag this problem should go away.

[rvanasa]

Thanks for the fix! How recently was the --no-install flag added to Mops? Since the extension uses an externally installed Mops version (rather than the version bundled with the extension), we could adjust the error message to encourage updating Mops if the command is unsuccessful.

[rvanasa]

Here is what I'm imagining (updating the error message slightly below the original code change):

throw new Error(
    `Error while finding Mops packages.\nMake sure the latest version of Mops is installed locally or globally (https://mops.one/docs/install).\n${err?.message || err}`,
);

The CI error should be fixable by running npm install in case that saves you a bit of time.

[ZenVoich]

How recently was the --no-install flag added to Mops? Since the extension uses an externally installed Mops version (rather than the version bundled with the extension), we could adjust the error message to encourage updating Mops if the command is unsuccessful.

In 0.45.0 a week ago. Maybe we should give it a time so fewer users encounter errors...

Here is what I'm imagining (updating the error message slightly below the original code change):

The CI error should be fixable by running npm install in case that saves you a bit of time.

Done

[ZenVoich]

Added mops version check

[rvanasa]

I just got a chance to check back on this. Thanks for the update! Merged.