Prototype memory allocator analysis

Still just dabbling with diagnostics
Adding docs, fixing APIs

We drop the dump format support -- not useful and conflicting if only
part of the functions can support it (i.e. not memory/1)
Adding sbcs_to_mbcs/0 function

This function checks the ratio of sbcs to mbcs block counts to
figure out if the lmbcs value for a specific kind of allocator
is too low.
Correcting calls usage

According to erlang:system_info/1 documentation, the format of
calls tuples is `{Key, GigaCalls, Calls}`. The module formerly
used only the `Calls` value, which would have given ridiculous cache hit
values if `GigaCalls` were to become used on a given node.
Improving documentation for recon_alloc

Adding tips and pointers of what to do to solve problems that can be
found using the functions, following helpful advice from @garazdawi.
The "main carrier" normally refers to the initial static carrier
Merge pull request #1 from garazdawi/patch-1

The "main multiblock carrier" refers to the initial static carrier
Improved documentation and glossary
Adding port_info/1-2 to recon

similar to recon:info/1-2, but for ports, with some port
implementation-specific stats included.

Also extends the recon_lib:term_to_port/1 accepted types.
Updating docs for port_info/1-2 functions
Fixing doc format for edoc
Merge branch 'allocators'

Conflicts:
	.gitignore
bump vsn to 1.1.0
v1.1.0 no longer a WIP
Remove the dot after "vs" for better doc output

12:50 nox: MononcQc: sbcs_to_mbcs/0: "compares the amount of single block carriers (sbcs) vs. the number of multiblock carriers (mbcs) for each individual allocator in allocator()."
12:50 nox: the first dot after "vs" makes edoc keep only "compares the amount of single block carriers (sbcs) vs." as the function summary
Merge pull request #2 from alco/patch-1

Remove the dot after "vs" for better doc output
Add snapshot functionality for offline inspections

When trying to debug memory issues it is not always possible to do
so on the target system. Snapshots in recon_alloc allows the user to
easily save a memory snapshot on the target node and then later analyze
it on some other machine.

The names of the functions in the API (i.e. snapshot_Action) was chosen in
order for the functions to be grouped in the documentation and not clutter
it.

See the documentation in snapshot_load/1 for an example use-case.
Bump to 1.2.0 -- Adding snapshots to recon_alloc

This commit does a few minor fixes to @garazdawi's snapshot addition by
adding a few export clauses, adding or changing the documentation a bit,
and bumping the version number to 1.2.0
Adding recon_alloc tests
Adding recon suite