Provide a Testcontainer for Neo4j.

[michael-simons]

I'd like to propose a Testcontainer for Neo4j, an open source graph database as in this pull request.

The test container is build with our official Docker image and provides the following features to the user:

• To retrieve a Bolt url for usage with one of the official drivers, most likely the Java driver
• To retrieve HTTP and HTTPS urls for the transactional REST api
• Especially to disable authentication or chose a password
• Also explicitly use the enterprise version of Neo4j

While we offer a test harness and users may opt to use an embedded version of our database during test, it seems that many people think it's a better practice to test any database access against "the real thing".

The container would be useful to us and allegedly to some other projects using Neo4j as well.

We have been using a container very similar while spiking our efforts of a reactive client for Neo4j.

[kiview]

Hey @michael-simons,
great PR and cool to see, that you are already using Testcontainers.

Just some small remarks, I'll give it a proper review later.

[rnorth]

This is a really nice PR, and a great addition to what is available for developers. Thank you.

I just have a couple of queries (pretty minor), but in general I think we'll be happy to accept this soon.
Cheers!

[michael-simons]

Thanks a lot for your detailed feedback everyone.

I have used the provided mechanism for accepting licenses (only necessary for our enterprise license).
I have kept the original test under an assumption, disabled as long as the user doesn't explicit add the license acceptance file.

I added AssertJ to check for exceptions in tests, also rewrote the older ones.

Note that I rebased onto your master, so you don't have to deal with merges.

[michael-simons]

I don't understand why CI fails now…

[rnorth]

I can't see a reason for that CI failure, but have re-triggered...

[rnorth]

Bizarrely it looks like we've suddenly been hit with this issue (or something like it): gradle/gradle#3318

This is obviously not a problem with the PR itself, so I'll have to investigate!

[rnorth]

Please could you rebase onto master/merge? I think we have fixed a strange problem on Travis CI in #1004, so this should resolve the failing build.

[michael-simons]

Done.

[rnorth]

The test failure has nothing to do with this PR - I'll tackle that with #1008. Please ignore!

[rnorth]

This looks good to me now. Thank you for the contribution @michael-simons!

[michael-simons]

Fantastic! Thanks for accepting my contribution.