This will familiarize users with the VS Code Problems
panel, and will also be used to verify that our
problemMatchers work fine when performing sanity checks
(which are based on the walkthrough)
For eng/ide/ada_language_server#1762
Querying 'textDocument/definition' on a source file mention
in a GPR file (e.g: 'for Main use ("main.adb")' now opens
the mentioned source file.
For eng/ide/ada_language_server#1733
And avoid having a non-fixed number of capturing groups, which can
cause troubles in some cases.
A big limitation though: VS Code does not seem able to
catch messages that have the same SLOC.
For eng/ide/ada_language_server#1723
Now all the problem matchers cat the parenthesis
(e.g: 'main.adb:3:3 (low)') and the semicolon format
(e.g: 'main.adb:3:3 low:').
We keep the old names for now to avoid breaking user-customized
tasks declared in tasks.json files: unfortunately there is no
proper deprecation mechanism for problem matchers in VS Code.
For eng/ide/ada_language_server#1723
This helps the user understanding that the command is
actually being processed, and allows to cancel it easily
if needed.
Also make the search bar placeholder smaller to make it always
visible no matter the size of the WebView.
For eng/ide/ada_language_server#1702
