Remove obsolete script
Update list of dependencies
RELEASES.md: update release-version.sh link

Updated for the move to scijava/scijava-scripts.
POM: use new bsd_2 license, not custom resolver

The license-maven-plugin 1.6 adds BSD-style license templates:
https://jira.codehaus.org/browse/MLICENSE-80

With this fabulous new addition, we can eliminate our custom
license resolver in favor of the stock bsd_2 license.
Update license and file headers

This was done using:
  mvn license:update-project-license license:update-file-header

The only real change is the loss of the legal disclaimer at the bottom
of the license. This disclaimer is not actually part of the BSD-2
license proper, but rather an addendum. For relevant discussion, see:
  https://jira.codehaus.org/browse/MLICENSE-80
Update mailmap
POM: tweak org name

We aren't actively using "ImageJDev.org" anymore. It was awkward.
POM: update developers and contributors

According to the Maven docs, the "developers" section is supposed to be
for active developers. Rule of thumb: people you would contact with
questions about the project. The "contributors" section is for people
who contribute(d) to the project, but who are not officially responsible
for it. So a few of the people formerly tagged as "developers" are more
properly listed under "contributors" instead.

Wayne Rasband and Lee Kamentsky are borderline (Wayne deserves no blame
for any crappiness in the ImageJ2 code!), but I think an argument can be
made for each to still be listed as a "developer" rather than a
"contributor" at this time.
POM: remove no-longer-needed configuration blocks

The removed sections have all migrated to the pom-scijava parent.
POM: simplify repositories blocks
POM: bump to pom-scijava 1.126
Remove add-header.sh script

The file header no longer matches LICENSE.txt, so this script is not
correct anymore.
check-headers.pl: fix copyright header checking

The LICENSE.txt file is no longer 100% identical to the header at
the top of each source file. As such, we cannot rely on an exact
comparison between the two. So let's relax the check to merely verify
that some sort of copyright header comment is present at the top.

This is OK, since running "mvn license:update-file-header" will
steamroll over any errors in such header comments anyway.
Update project licenses

This was done using:
  mvn license:update-project-license

The only real change is the loss of the legal disclaimer at the bottom
of the license. This disclaimer is not actually part of the BSD-2
license proper, but rather an addendum. For relevant discussion, see:
  https://jira.codehaus.org/browse/MLICENSE-80

See also dcb4444d063efb4c1e707edf514f2ff7779dbb42.