Added workspace name validation: the extension will only work if the workspace name is MQL4 or MQL5

[Akress-spec]

Now I have some subfolder as workspace, shared project/XXXX, nothing working.
Why is it forced to use hard workspace names.

This feature makes MQL-tools unusable :(

[itradeaims1]

Yep, is there a work around?

[Akress-spec]

I found a couple of workarounds.

But the best is to use mqltools 2.1.0.

But now I see an all-time notification in VS Code that mqltools is not up-to-date. I really don't like this kind of notification. Maybe there is a way to switch this off. My tools should be all-time up-to-date; otherwise, I have some kind of bad feeling.

Also, I tried to change the code of 2.2.0 and fix this issue with workspace checking, thanks Copilot. That worked. But styler didn't work anymore, and I also got a notification that mqltools is not up-to-date.

I would prefer if the mql tools guys changed the feature workspace check. For example, mql4 or mql5 should be present somewhere in the parent path. And not expect only one spacial name of Workspace.

On the other hand, I really don't understand why the workspace should only have the mql4 or mql5 name. To differentiate if working in mql4 or mql5? There are other ways to check this. Or maybe it is necessary for guys who are working with Mac?