Codechecker

:hammer: Improvements
* **Refactor report tree** (112)
Refactor the report tree's code.
Display depth of report steps.
Group reports by severity levels.
* **Add Go to docs button to sidebar** (109)
The documentation URLs are fetched by running CodeChecker checkers at project load.
* **Add architecture.md** (105)
Adapted from my private notes with minimal changes, but should be fine for this purpose.
The image can be edited via https://draw.io/.
* **Integrate CodeChecker log into executor** (108)
Fixes (38).
Instead of running CodeChecker log as a separate process, it is now integrated into the `backend/executor.
Added commands, build tasks, UI buttons for running CodeChecker log.
Added settings to specify custom args as well as a build command, which can be overridden by commands or tasks.
Added a couple tests for the backend.
:bug: Bug fixes
* **Improvements for handling CodeChecker version checks** (114)
* **Fix handling of removed processes from the execution queue** (110)
* **Refactor keyboard navigation** (106)

For more information check the [milestone](https://github.com/Ericsson/CodecheckerVSCodePlugin/milestone/4).

:hammer: Improvements
- **Better range positions for reports** (96)
If no range information is available for a report (for example in case of `clang-tidy`) we will use the VSCode API to get word position at the given line + column position and use it to highlight the location of the report.
- **Hide codelens and bug step decorations when document is dirty** (93)
If there are unpersisted changes in the current document we will hide the provided codelens items and bug step decorations.
- **Deduplicate scheduled tasks based on command line** (95)
If the same file is being saved multiple times while the analysis is ongoing, do not add the re-analysis of the same file multiple times to the analysis queue, because it is superflous.
- **Change CodeChecker analysis output to `.codechecker/reports`** (91)
`.codechecker` directory may contain compilation database which is generated by the `CodeChecker log` command. It may also contain other files in the future. For this reason we changed the output folder of the `CodeChecker analyze` command to `.codechecker/reports`.
- **Highlight bug step ranges when a bug is selected** (88)


:bug: Bug fixes
- **Refactor executor to pass shell arguments as array** (57)
- **Change value of version process type to analyzer-version** (97)
- **Expand user in the CodeChecker binary path** (98)

For more information check the [milestone](https://github.com/Ericsson/CodecheckerVSCodePlugin/milestone/3).

:hammer: Improvements
- Show checker name in the bug tree for each report (68)
- Add icons to the statusbar text (67)
- Change required VSCode API version to `1.53.0` which is supported by the latest Theia editor (83)
- Extend the help of the analyzer arguments configuration option (82)
- Rename `Database path` to `Compilation Database Path` (81)

:bug: Bug fixes
- Fix showing diagnostics in the `Problems` pane (70)
- Check supported `CodeChecker version` when the `CodeChecker` executable path configuration setting is changed (69)
- Fix showing output channel in `Theia` editor (84)
- Fix keyboard navigation commands (75)

For more information check the [milestone](https://github.com/Ericsson/CodecheckerVSCodePlugin/milestone/4).

:hammer: Improvements
- **Find compilation database automatically in the project** (52)
The extension will try to find compilation databases (`compile_commands.json`, `compile_cmd.json`) automatically in the following directories:
- `$WORKSPACE_DIR/.codechecker`
- `$WORKSPACE_DIR`
- `$WORKSPACE_DIR/build`
- **Keep active repr. steps open when switching files** (60)
If we click on a report step which refers to a different source file (e.g.: *lib.h*) than the currently opened file (e.g.: *main.cpp*), the plugin will show the reports from that file but will keep the selected report in the bug tree.
- **Remove unclosable CodeChecker analysis in progress window** (64)
On large projects the analysis may take huge amount of times (e.g.: minutes). In this case it is really annyoing for the user to show an unclosable pop-window. Also this information whether an analysis is running already available in the bottom bar. For this reason we removed this pop-up window but introduced a new tree item on the overview sidebar to stop the analysis.

:bug: Bug fixes
- Set priority order for settings items (55).
- Wait for terminal initialization for CodeChecker log command (54).
- Reduce number of parse calls (58).
- Fix adding selectedEntry to openedFiles (63).
- Use matrix strategy at deploy github action (48).
- Remove fast-plist dependency (53).

For more information check the [milestone](https://github.com/Ericsson/CodecheckerVSCodePlugin/milestone/2).

:tada: CodeChecker VSCode plugin
Today we are proud to announce the first official release of [CodeChecker](https://github.com/Ericsson/codechecker) VSCode plugin.

:star2: Main features
- Run CodeChecker analysis from the editor and see the results automatically.
- Re-analyze the current file when saved.
- Commands and build tasks for running CodeChecker as part of a build system.
- Browse through the found reports and show the reproduction steps directly in the code.
- Navigate between the reproduction steps.

:computer: Trying It Out
1. [Install CodeChecker] version `6.18.2` or later and optionally add it to the `PATH` environment variable.
2. Install CodeChecker extension from the [Visual Studio Marketplace], from [Open VSX] or download manually from [Downloads].
3. Check the path to CodeChecker and set your preferred command-line arguments - see [Configuring CodeChecker] for more information.
4. Open your project, and run an analysis, or browse through the found reports!

[Install CodeChecker]: https://github.com/Ericsson/CodeChecker#install-guide
[Visual Studio Marketplace]: https://marketplace.visualstudio.com/items?itemName=codechecker.vscode-codechecker
[Open VSX]: https://open-vsx.org/extension/codechecker/codechecker
[Downloads]: https://github.com/Ericsson/CodecheckerVSCodePlugin/releases
[Configuring CodeChecker]: https://github.com/Ericsson/CodecheckerVSCodePlugin/blob/main/README.md#configuring-codechecker

For more information about this release see the [milestone](https://github.com/Ericsson/CodecheckerVSCodePlugin/milestone/1).

Major architectural changes!

Lot of architecture changes were made to simplify the way how the plugin runs the analyzers through CodeChecker and parses the results. This should increase the plugin performance and stability.

Changes
* Support CodeChecker v6.8 and v6.8.1 to run the analysis.
* Remove of the CodeChecker backend server 115 116
CodeChecker server instances were required to run in the background for each project, this added a lot of extra complexity to the plugin. With the new architecture CodeChecker is only used to run the analysis and the plugin parses the generated plist reports.
* CodeChecker service api layer was removed
The CodeChecker server api layer is not needed in the new plist parsing architecture
* Easier version increment
No manual xml modification is required to increment the plugin version.
* General documentation and source code comment improvements