OpenSystemsDevelopment / qpdf

This is just QPDFJob wiring.

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

This commit contains the changes from generate_auto_job based on
manual changes from the previous commit.

Rather than adding yet another flag that is almost never useful on its
own, just have --remove-restrictions disable digital signatures. The
operations are still separate in the API.

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

Avd xcsv brvtns.

* 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)

Update getJSON() methods and calls to them

This makes it much more convention to use the initializeFromArgv
functions since you can use string literals.

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.