Without this, call to decode with copy_strings option in an
application will make Dialyzer complain when using the exported type for options

Some users of Jiffy have experienced issues when decoding large JSON
documents. Normally Jiffy expects smallish documents and returns any
strings as sub-binaries. When dealing with large documents these
sub-binary references can keep a large amount of RAM around unless the
user goes through and applies `binary:copy/1` on every string returned
from Jiffy. This however causes a large amount of CPU usage to do
something that Jiffy could do as it builds the JSON structure.

The `copy_strings` decoder option does exactly this. Instead of
returning sub-binaries Jiffy now copies every string into a newly
allocated binary. Users report that this fixes the memory issues while
also not negatively affecting performance significantly.

You can no optionally request that keys are deduplicate inside of Jiffy
instead of having to perform that operation in Erlang.

When "\u"-escaping a Unicode character, the esc_extra value doesn't
need to include the number of bytes in the input string.  That is, if
a three-byte UTF-8 character is being escaped to a six-byte "\uXXXX"
sequence, esc_extra only needs to be increased by 3.

Cleanup after new enc lands

For some reason I left a 377KiB test case checked in. Replacing this
with a generated test case is obvious in hindsight.

Windows appears to not enjoy relative path names for exectuables so
hopefully this fixes things there.

Fixes #83

Apparently hex only includes some files by default but not others
rather than a sane default of anything except for VCS directories. So
now I also get to maintain a list of files in my .app.src.

Apparently rebar3 can't generate a sane version number from Git tags and
adds a bunch of BS build number and ref tags which hex.pm then rejects.
Given that I can't find any documentation on how that works and reading
code is an exercise in over engineered abstractionism I've succumbed to
the demoralizing conclusion that I'll just have to go back to the dark
ages and maintain my versions both in source and in version control.

A call to `jiffy:encode(Term, [use_nil]).` will currently cause dialyzer
to issue a warning because `use_nil` is not included in `encode_option`.
This appears to just be an omission.

Add support for rebar3

Allow Jiffy to be used easily in projects using either rebar 2 or 3.

PropEr broke my support for R14. Turns out that EQC Mini is quite usable
so I've just switched to that. If EQC Mini exists it will be used, if
not the test is skipped gracefully.

Originally reported by @NorthNick on apache/couchdb-jiffy.

Fixed wrong jiffy:decode/2 spec

Previously if a key was malformed UTF-8 and the user specified the
`force_utf8` option we would fail to try and encode a fixed up version
of the object. This was due to missing a clause to catch the
`invalid_object_member_key` exception. This adds the clause and a couple
tests to ensure it works.

This was marked in the c_src/double-conversion directory but I've gone
ahead and added a copy to the root LICENSE file.

Time for Jiffy to enter the world of Erlang package management.

Destroy map iterators once we're done with them.

Each call to enif_map_iterator_create() must be paired with a call to
enif_map_iterator_destroy(). Otherwise, we'll leak memory.

Fixes #112

rebar.config: set CFLAGS/CXXFLAGS/LDFLAGS on Hurd

The environment variable approach breaks other projects' Travis-CI runs
if they include other projects that depend on a different version of
PropEr.

Fixes: #106

Use the common CFLAGS/CXXFLAGS/LDFLAGS used on Linux/FreeBSD/etc also
on GNU/Hurd.

Fix win32 build

This test has proved its point and now just exists to randomly fail some
builds depending on race conditions with the garbage collector.

I was being lazy and relying on Travis. This fixes up the map spec for
newer VMs.