feat: no remote fetch when IDE gets CLI version

[kittaakos]

Motivation

To speed up the load time of the About dialog in IDE2. As requested in #1572, IDE2 reads the CLI version from the package.json.

Change description

• 2.0.3:

  

• A dev build with the changes:

  

• Local IDE2 build with the changes:

  

Other information

If the CLI version is a pinned commitish and not a semver, IDE2 will show the commitsh.

Assuming the following pinned CLI version:

diff --git a/arduino-ide-extension/package.json b/arduino-ide-extension/package.json
index 1b7cc2de..ab4414ea 100644
--- a/arduino-ide-extension/package.json
+++ b/arduino-ide-extension/package.json
@@ -159,7 +159,7 @@
   ],
   "arduino": {
     "cli": {
-      "version": "0.29.0"
+      "version": "alma"
     },
     "fwuploader": {
       "version": "2.2.2"

The expected About dialog (with a dev build) is:

Closes #1572

---

It should be possible to run arduino-cli version --no-fetch or similar to avoid checking for updates. I have never used a CLI tool before that does a silent remote fetch when getting the only version. If there is a good example, please let me know. CLIs usually warn about the outdated version (brew, npm, yarn, etc.) when users execute a command that requires the Intenet connection. The Arduino CLI ought to warn the user on core index-update or lib install but not on version.

Reviewer checklist

• PR addresses a single concern.
• The PR has no duplicates (please search among the Pull Requests before creating one)
• PR title and description are properly filled.
• Docs have been added / updated (for bug fixes / features)

[per1234]

Thanks Akos!

[AlbyIanna]

LGTM ✅

On a side note though, I have noticed that this change breaks the localized string "arduino/about/detail" when the ide language is one that has that string already translated. That happens because the number of parameters used the localized string changed from 7 to 5.
For example, if you set the language to "Italiano", you get this dialog

Anyway, I won't request changes in this PR because I'm not sure how we should proceed about this kind of localization issues.