sel4utils: Mapping deferred rights reservations

Updated sel4utils to support the new vspace interface function:
'vspace_deferred_rights_map_pages_at_vaddr_fn'. This enables the
user to pass in the rights of the memory region when mapping a
'rights deferred' vspace reservation.

sel4utils: Deferred rights reservation creation

Updated sel4utils to support the new vspace interface function:
'vspace_reserve_deferred_rights_range_at_fn'. This enables the
user to create vspace reservations without passing the rights of
the memory region. The rights being deferred to the mapping
invocation.

Trivial: Style fix

make the style checker happy

seL4_libs: remove autoconf.h from seL4_libs

this commit removes autoconf.h generation from each lib and
append '#include <<lib_name>/gen_config.h>' after each
'#include <autoconf.h>' since autoconf.h is only the for the
kernel config now. This is a temporarily solution, since we
currently don't have a way to tell which header files each file
is trying to include when it includes 'autoconf.h'

pragma once and for all

SELFOUR-1053: Invoke VMM layer directly in vpsace_[new/map]_pages()

This change brings the behaviour of vspace_[new/map]_pages() in line with its
expected behaviour as the OS page-level combinatorial allocator -- such an
allocator is expected to directly call on the PMM and VMM for frames and pages
respectively, then map the frames into the pages, and do some book-keeping
before handing out the new vmem to userspace.

The previous implementation of vspace_[new/map]_pages had a call to
vspace_new_reservation which in turn had a call to malloc somewhere internally,
and this was causing a circular call path in our libraries.

Fix all the whitespace

- remove trailing whitespace
- remove duplicate blank lines
- remove blank lines at end of files

vspace_new_pages: New configuration behavior

Fix licenses

libsel4utils: Correct type in printf

sel4utils: Print error when vspace update fails

SELFOUR-567: use seL4_CapRights_t

sel4utils: Fixed memory leak in vspace impl

As an optimisation, the implementation of vspace in libsel4utils keeps
track of the last vaddr it allocated or freed. This is used as a
starting point for finding regions of unallocated addresses. Prior to
this change, when a range of addresses was freed, this vaddr was set to
the end of the range. This was a problem because newly freed addresses
earlier in the range will never be reused. This fixes the problem by
setting the last allocated/freed vaddr to the start of a newly freed range.

libsel4utils: Collapse some unnecessary forward declarations.

libsel4utils: Use correct entries when subdividing tables

When inserting a new book keeping level the default entries on that
level should be that of the entry it is being inserted into. For example,
if a top level entry was RESERVED, and part of the region needs to be
marked as mapped (resulting in needing to add a new level to effectively
split the RESERVED into part RESERVED and part mapped) then the parts
that are not made mapped should be left RESERVED, not marked as EMPTY

libsel4utils: Rewrite vspace for 64bit support

This involves a nearly full rewrite of the internals of the vspace
implementation. The core reason for the rewrite was to go from a
fixed two level book keeping structure, to a multi level book
keeping structure.

all: s/LOG_*/ZF_LOG*

libsel4vspace/utils: use uinptr_t instead of doing undefined void * arithmetic

libsel4utils: fix bug in vspace implementation where large page regions could be handed out even though they already contained allocated regions of a smaller page size