[kernel] fix ast-diff on code with forward-decl of struct

Closes #1164

See merge request frama-c/frama-c!3908

Fix missing shared files in installation

See merge request frama-c/frama-c!3866

[lint] fix identification of files that have been subject to git mv

See merge request frama-c/frama-c!3917

[Wp] doc: recalls the name of the default anonymous behavior

Closes #2631

See merge request frama-c/frama-c!3918

[test] Fixes promoting when using test script

Closes #1153

See merge request frama-c/frama-c!3898

[eva] enable apron tests (dune)

See merge request frama-c/frama-c!3716

[Makefile] export WP cache-related Makefile variables to commands

See merge request frama-c/frama-c!3895

Take into account more git statuses in commit hook linter

See merge request frama-c/frama-c!3912

[Eva] Bug fix in the "smashed" function of trace_partitionning.ml

See merge request frama-c/frama-c!3910

[doc] remove rebellious @plugin tags

See merge request frama-c/frama-c!3909

supports pattern such as

```c
enum {
     TAG1 = 42,
     TAG2 = TAG1 << 3
};
```

The function relied on "List.map" which is not tail-rec. With enough
plevel, it provoked a stack overflow. I've simply fixed it by performing
the mapped computation inside the fold directly.

In presence of the following pattern of code:

```c
struct S;
enum { t = 1 };
struct S { char[t]; };
```

-ast-diff will attempt to compare the use of `t` in the field declaration
before having visited the `enum` definition. Thus, we can't rely on an enumitem
being present in the correspondance table when looking for a correspondance.