…ake) (#124)

…r wow64 (#127)

This moves the `human` functions in their own headers and also simplify the way they can be used; they now return specific types that have their own `fmt::print` formatter which makes it easy to dump them on `stdout`. Prior, the caller needed to capture both the amount and the unit. This also fixes #145.

Use `v3` instead of `v2` to get rid of those warnings:
```
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: actions/checkout@v2, actions/upload-artifact@v2
```

This adds edge coverage (--edges) for the `bxcpu` backend (it also picks up a new build of `bxcpu`, & remove the `aggregate.cov` file generation).

Co-authored-by: 0vercl0k <1476421+0vercl0k@users.noreply.github.com>

I was profiling `wtf` and found a behavior that I wasn't aware of. Basically, every calls we make to `aligned_alloc` allocates 8kish instead of 4kish. For whatever reason, I made an assumption that it would use a special allocator; it isn't a special allocator it just wraps a call to `malloc` with that math: `v5 = malloc(Alignment - 1 + Size + 8);`. In our case, both `Alignment` & `Size` are `0x1000`.

I switched the calls to `aligned_alloc` to `VirtualAlloc` / `mmap` to match the behavior that I wanted in the first place. We also don't need page aligned chunks in the `Ram_t` object, so I turned this one into a `malloc` call.