No commit message

No commit message

When a dollop with small fallthroughs would fit entirely in an 
allocated region but some of those fallthroughs are already placed,
coalescing would miscalculate what to do. It would say, "Let's
place it all" but would eventually want to put a jmp to the 
already-placed dollop. When the fallthoughs were small, that 
jump would be bigger than the entirety of dollop and cause
us to overflow the reserved space.

Add plugin support for
1. Plugins to retarget pins

2. Plugins to disallow coalescing dollops that they address.

1. Allow AddressDollop() to tell Zipr whether
the dollops should be coalesced. Defaults to true.

2. Allow the plugin to retarget a pin.

Give the source address for the instruction
that is targeting the dollop to be placed. This
will give another signal to placement plugins
to help them make a decision.

Allow for reserved ranges to be plopped. Ie, selectively
call Reserve when plopping bytes instead of always doing it.

This fixes a bug where dollop creation incorrectly
continued past IBTs. IBTs should always start a
dollop and this fixes that.

Any patch whose target immediately follows can be
turned into a five byte nop. This is not 100% ideal
but it is a good start to test whether this optimization
is worthwhile.

fixed unpinned and pinned unresolved dollop's to sort by instruction's address instead of instructions' base id.  sorting by baseID was non-deterministic when both isntructions were not in the database.

When the memory space is asked for nearby ranges,
it should return a range.