Update release notes for 5.0.4
Update 5.0.4 date and add mention of PicoQuant support
Fix CLI tools when used from a source working copy

There is no longer a bio-formats.jar. We can use formats-gpl.jar
instead, which references the others in its manifest Class-Path.
Add missing dash
Update build script to correctly pass Sphinx options to Ant
Update auto-generated documentation

Repository: openmicroscopy/bioformats
Already up-to-date.

Generated by BIOFORMATS-5.0-latest-docs-autogen#274 (http://ci.openmicroscopy.org/job/BIOFORMATS-5.0-latest-docs-autogen/274/)
Add branch-specific link for downloading the JAR file if unfound
Also modify link in bf.bat
Merge pull request #1300 from snoopycrimecop/dev_5_0/latest/autogen

Update auto-generated documentation
Merge pull request #1281 from melissalinkert/5.0.4-version-history

Update release notes for 5.0.4
Merge pull request #1298 from ctrueden/fix-cli-dev

Fix CLI tools when used from a source working copy
Merge pull request #1301 from sbesson/tools_download_link

Add branch-specific link for downloading the JAR file if unfound
PrairieMetadata: keep reference to element parents

Specifically, each <File> now knows its <Frame>, and each <Frame> now
knows its <Sequence>. This will useful for handling the more compact XML
structure of PrairieView 5.x, in which parameter values are inherited
from parent elements where feasible.
PrairieReader: avoid NPE when CFG file is missing
PrairieMetadata: add an attribute accessor method

This returns null when the attribute is not present, rather than the
empty string. It also makes the code slightly shorter.
PrairieMetadata: add data structure for key/values

The key/value pair structure got more complex in PrairieView 5.2. Now
each key can point at either a single string item, or at a table of
values, which can themselves point at sub-tables.

This data structure is intended to facilitate easy management of the
new structure, while still supporting the old structure, too.
PrairieMetadata: add helpful helper methods

These are useful when dealing with possible null values.
PrairieMetadata: use ValueTable as appropriate
PrairieMetadata: parse old-style keys into tables

As of PrairieView 5.2, the key/value pair structure is more
hierarchical, with value tables able to contain sub-tables.

Let's parse the old-style keys in the same way, so that regardless of
which version of PrairieView wrote the data, it can be consumed in the
same way after parsing.
PrairieMetadata: rename field, to avoid ambiguity

We are going to add additional ValueTable fields in other places,
and calling them all "values" gets confusing (and causes IDEs to
emit warnings about variable names shadowing one another).