Just using `check` as a prefix to various keywords would lead to too many
ambiguities in the parser (notably in contracts, where you can have an empty
requires list followed by `check ensures ...` or a `check requires ...`. With
a lookahead of 1, it's difficult for the parser see which rule should apply.
Hence, the lexer will perform itself the lookahead and emit a proper token
(`CHECK_ENSURES` or `CHECK_REQUIRES` respectively).

this is a generalization of `check` vs. `assert` to other annotations. Not all
annotations are relevant though. Currently, there are more annotation nodes in
the AST that can have a flag `{ tp_only_check }` than was deemed useful in
pub/frama-c#25, but said flag can in fact safely be ignored. Moreover, this
commit only add this flag in the AST, but provides no further mean to set it to
true except for the original `check` keyword (i.e. on `AAssert`). The parser
and the behavior of the plugins that can handle the flag will be updated in
subsequent commits

These aliases will not be printed in the help message of Eva, and will emit
a warning when used.

Invisible aliases are not printed in the help message of the plugin or kernel.
Deprecated aliases emit a warning when used.

Applies the concrete operator on all possible pairs of integers.
This is maximally precise.