Tags

- #46: Change API for `snippet_for_file` to make it slightly more generic (several substitutions are now possible).
- #47: Fix a bug related to `snippet_for_file` which wasn't working for cppyy/cppdef magic.

- !37 Provide a mechanism to enable that the cell displays only a part of a larger file, for cppyy, compilers and
clang-tidy magics.
- `print-command` option has been renamed `print_command` so that the provided help message helps (previously
there was a mismatch between option name and variable name and the error message was misleading as a result).
- Fix ruff and mypy (in strict mode) warnings.

- #41, #43: A mechanism to provide flags to magics has been added and used to provide an optional `-p` flag
telling whether the terminal command should be printed in the outputs or not.

First stable release of CppyyKernel, which provide solutions to many issues
we had identified when the v0.1.0 was published.

Our first goal is met: our [C++ training](https://gitlab.inria.fr/formations/cpp/gettingstartedwithmoderncpp)
may now be run entirely with the kernel (this is not yet the case for its main branch as the MR that will
provide the update was stalled until the present tag is published)

- #28, #25, #40, #36, #32, #33: Introduce magics to be able to run content of a given cell directly with a command line tool (be it
a compiler such as `gcc` or `clang`, a tool such as `clang-tidy`). The cell must provide all the context. This
functionality enables to limit drastically the use of online compilers in our C++ training.
- #3: Magics are now provided to enable `std::cin` within a notebook (a dialog box is opened).

- #5, #6, #9, #16, #27: Improve the management of warnings and error messages.

- #8, #34: Provide a hacky way to mimic `assert` behaviour. It is explicitly underlined when used that it is a
hack that might not work in all configurations.

- #7, #10, #13: Introduce a magic `cppyy/cppdef` to use explicitly under the hood `cppyy.cppdef` instead of the
`cppyy.cppexec` we use by default for conveniency. Some C++ operations require the finer `cppdef` (the
cases we have identified are underlined in `notebooks/Cppdef.ipynb` notebook.

- #14, #15, #20, #22, #26, #38, #39: improve tests, CI, deployment, Docker and various dev tooling of the project.