Move README includes

Fixes #718

Per
https://github.com/exercism/docs/blob/ccdf58f97f698c265f0f67fa7cb9d94084d7f0a3/language-tracks/exercises/README.md#files

change: update to v1.1.0 tests

Move readme insert

Fixes #720 replace lambda with method ref

This reverts commit 43e792bf55f3e53ae696b8480ba8fe73bac5bba0.

Remove unused images

Fixes #716 remove redundant type params

Fixes #696

Fixes #737

Use string builder over looped string concatenation.

ABOUT.md: remove confusing sentence

ABOUT.md: update formatting for Nextercism

[WIP] Adds additional test for two-fer exercise

Choose core exercises

house: add to track

Update config.json to set which exercises are core and which ones are
unlocked by other exercises.

Fix broken link - exercism.io: Installing Java

Series example refactoring

I fixed the link path to end in "installation" instead of "installing"

Use Collections.singletonList in custom-set tests

Fix spelling errors in custom-set, word-count test names

Update gitter webhook for travis integration

Add default maintainers file

We wish to feature the maintainers of each track on the new (nextercism) website. Ideally, the bios will be tailored to each track, giving a friendly view into each maintainer's background and interest in the language, and even (perhaps) what they enjoy most about maintaining the track, or what type of things they tend to focus on.

The main reasons for including these are to:

* provide a stronger basis for empathy with maintainers
* give well-deserved recognition
* plant a seed in people's minds that _Exercism tracks are maintained by people like me... I could do that!_

Being featured on the Exercism website is entirely optional, and we're generating all the data with show_on_website=false so that if you don't want to bother, you don't have to change anything.

If you've moved on, or decide to do so, please submit and merge a PR (for visibility to the others involved) that sets **alumnus** to _true_ for your maintainer entry. I'm working on a bot that will update the GitHub team to reflect the current state of this file.

We can merge this as is, and any changes can be added in subsequent pull requests.