OpenSystemsDevelopment / qpdf

This change updates all occurrences of `std::endl` to `\n` across various files for improved efficiency and consistency. It reduces unnecessary flushing of output buffers associated with `std::endl` while maintaining the same output format.

This improves indentation of long strings. This commit also fixes some
trailing whitespace in ChangeLog.

Use std::vector instead of list and move shared pointers

This is just QPDFJob wiring.

...since they have to be handled before other options. It was working
because, in both cases, `file` was alphabetically before the other
keys, but this implementation gives a stronger guarantee.

Accept --file and --range as named parameters in additional to
allowing positional arguments. This is in preparation for adding
additional flags.

This commit contains only the manual changes. It is separated for
clarity. This commit would not pass CI because it lacks the automated
changes, which appear in the next commit.

Add the command-line arguments. They don't do anything yet.

Using search and replace.

* Replace --create-from-json=file with --json-input, which causes the
  regular input to be treated as json.
* Eliminate --to-json
* In --json=2, bring back "objects" and eliminate "objectinfo". Stream
  data is never present.
* In --json-output=2, write "qpdf-v2" with "objects" and include
  stream data.

Also add stubs for top-level QPDF methods (createFromJSON,
updateFromJSON)

Change .clang-format and commit automated changes from a fresh run of
format-code

Run this:

for i in  **/*.cc **/*.c **/*.h **/*.hh; do
  clang-format < $i >| $i.new && mv $i.new $i
done

Changing from bool requiring true to string requiring the empty string
is more consistent with the CLI and makes it possible to add an
optional parameter or choices later without breaking compatibility.

Flatten everything to make it easier to map command-line flags to
json. The old structure was an illusion anyway because there was no
mechanism to enforce that things were in the right place. This also
helps with future flexibility.

Use "file" consistently for specifying a file path. We use "filename"
when adding attachments for a completely different purpose.

The code was assuming everything was happening inside dictionaries.
Instead, make the dictionary key handler creatino explicit only when
iterating through dictionary keys.

Now still have to go through and implement the handlers.