OpenSystemsDevelopment / qpdf

I thought /EFF was supposed to be used as a default for decrypting
embedded file streams, but actually it's supposed to be advice to a
conforming writer about handling new ones. This makes sense since the
findAttachmentStreams code, which is not actually needed, was never
right.

For now, --allow-insecure allows creation of files with the owner
passwords empty or matching the user password.

When removing unreferenced resources, notice if a page (recursively)
contains a form XObject with unreferenced resources, and count any
such resources as referenced by the page.

Refactor in preparation for resolving unresolved resources in form
xobjects from page.

Warnings were not being handled per --no-warn or generating exit code 3.

We need to use token.getRawValue, not token.getValue

Keep a std::pair internal to the iterators so that operator* can
return a reference and operator-> can work, and each can work without
copying pairs of objects around.

Use the first of ASCII, PDFDocEncoding, or UTF-16 that is capable of
encoding the string.

Add constructors that take a QPDF object so we can issue warnings and
create new indirect objects.

Create a computationally and memory efficient implementation of name
and number trees that does binary searches as intended by the data
structure rather than loading into a map, which can use a great deal
of memory and can be very slow.

If we ever had an encrypted file with different filters for
attachments and either the /EmbeddedFiles name tree was deep or some
of the file specs didn't have /Type, we would have overlooked those as
attachment streams. The code now properly handles /EmbeddedFiles as a
name tree.