* siri/cdv/div-bugfixes/OTP-15391:
  [cdv] Handle multiple "Yc" lines refering to the same refc binary
  [cdv] Speed up reading of dump with many processes

Co-authored-by: Siri Hansen <siri@erlang.org>

Usually, sub binaries are implemented as special sub binary terms
("Ys" lines). But if a sub binary is sent to another process, sub
binaries will be eliminated and incorporated into the ProcBin ("Yc"
line), and when that happens there can be several "Yc" lines that
refer to the same underlying binary object. Make sure that that the
crash dump viewer can handle multiple "Yc" lines referring to the same
binary object.

Literal maps with complex keys such as:

    #{"one"=>1,"two"=>2,"three"=>3,"four"=>4}.

would produce a crash dump that `crashdump_viewer` was unable
to read.

https://bugs.erlang.org/browse/ERL-722

This commit replaces the old memory instrumentation with a new
implementation that scans carriers instead of wrapping
erts_alloc/erts_free. The old implementation could not extract
information without halting the emulator, had considerable runtime
overhead, and the memory maps it produced were noisy and lacked
critical information.

Since the new implementation walks through existing data structures
there's no longer a need to start the emulator with special flags to
get information about carrier utilization/fragmentation. Memory
fragmentation is also easier to diagnose as it's presented on a
per-carrier basis which eliminates the need to account for "holes"
between mmap segments.

To help track allocations, each allocation can now be tagged with
what it is and who allocated it at the cost of one extra word per
allocation. This is controlled on a per-allocator basis with the
+M<S>atags option, and is enabled by default for binary_alloc and
driver_alloc (which is also used by NIFs).

* siri/cuddle:
  [cdv] Fix test of size limit reached on crash dump, again