Resolve the order of dependencies in the clike language backend.

[flaviojs]

It can reorder dependencies and add forward declarations.
Warns if there is stuff that it cannot resolve.

Includes inner-working traces that can be seen with cbindgen -vv (should be left there to facilitate future changes).

Includes tests for assumptions that ResolveOrder is making.

Includes a clippy MSVR change to 1.74 (same as Cargo.toml) to fix a warning.

Fixes #43

Maybe replaces #1028 ?

---

Before this I had to add extra stuff in after_includes for about 10% of symbols that ended up in items. All those are handled, leaving only the cases where reordering items and adding forward declarations cannot fix the problem (like constants used in structs appearing after the items are written).

I'm sure there are C/C++ cases that are not being handled, but the documentation and tests should facilitate implementing whatever is left.

I reeeally wanted to do some refactoring to facilitate changes and add documentation before attempting this, but the "single person reviewing and approving" bottleneck prevents that solution. I reached a point where it's impossible to continue developing without adding a hack or implementing something like this.
@emilio if there is a proper way for PRs to signal they are "ready to review" after your initial review is done and more changes are applied, please document it somewhere. =~~

[flaviojs]

Had to remove the auto-declaration code, which caused unexpected problems.
This means more declarations, which is fine as long as the header compiles.

Ideally, the resolver should be fuzzed to make sure different initial orders are always compilable.