pangram: implement missing test [Fix #314]

* Simplify construction logic for palindrome products

Fixes issue #283

* Refactor palindrome test comparator into a named function

Change order and names of anagram tests

* Added list-ops exercise to the Java track
* Removed NetBeans settings from the project dir
* Added collect() operation and tests

* Remove deprecated problems key

    This should have no effect on the track since the problems key is
    long-deprecated, see https://github.com/exercism/x-api/pull/137 for
    confirmation.
* Reorder exercises array to match initial difficulty rankings
* Assign integer difficulties to all ranked exercises
* Adjust difficulty rating and position of grade-school

change: add to track

hamming: make test names consistent [Fix #304]

Build jq from source.

- we need version 1.5 and can't get it from the official repo.
- includes adjusting the PATH so that our tools (like jq) get
  precedence.

Issue #306: fix spelling mistakes in test names

*Remove mention of "complete"

*Fix spelling mistake in second test

*Add throws Exception to methods that throw exceptions

Migrate to JUnit @Rule in triangle exercise [Fix #268]

Nucleotide-count: use JUnit's @Rule feature [Fix #264]

Pascals-triangle: use JUnit's @Rule feature [Fix #265]

Simple-linked-list: use JUnit's @Rule feature [Fix #267]

Nth-prime: use JUnit's @Rule feature [Fix #263]

Series: use JUnit's @Rule feature [Fix #266]

Allergies: remove redundant array creation [Fix #275]

Change @Test expected parameter to @Rule ExpectedException in hamming [Fix #262]

Change test names to Camel case

luhn: update to latest canonical tests

Issue #154: make journey-test.sh use exercises

Issue #276: linked-list: Rename Deque to DoublyLinkedList

Previously this code was applying the required operations to every
second digit starting from the LEFT. The correct solution applies the
required operations to every second digit starting from the RIGHT. The
fact that this was not caught by the tests is a problem! The canonical
tests have been updated since this exercise was last overhauled, so next
steps should be to update to match the expanded canonical test suite,
then test against a broken implementation to see if it is now caught.
Even if it is, it may be worth including an explicit left vs right test
in the canonical suite if one does not already exist.