Deprecate old lifecycle methods

[LMnet]

testcontainers-java reworked lifecycle of the containers a bit. This pull request is to support these changes.

• New TestLifecycleAware trait introduced. It's a copy of java's interface, but with scala's Option type. Users of the library can use it when they want to do something with the container before or after the test. Personally, I'm against this feature at all, but I didn't convince the core java team that this feature is redundant. So, we have to support this. Also, I could just reuse java's interface, but I don't think that it's a good idea. Scala's hierarchy is completely separate from the java's, and it would be very unnatural for the scala users to work with the java's Optional.
• Container now implements Startable java interface with start and stop methods.. I didn't copy this interface, because it's absolutely minimal and usable from the scala side.
• ForEachTestContainer and ForAllTestContainer now uses new lifecycle methods.
• They are also a bit improved internally. These improvements are based on my work on the new API, but not related to the new API directly:
  • I handled few multithreaded corner cases with volatile.
  • Improved test description for error messages.
  • ForAllTestContainer now supports afterTest/beforeTest.
• SeleniumContainer now implements TestLifecycleAware.
• MultipleContainers and LazyContainer are implements TestLifecycleAware too, because they could contain containers with TestLifecycleAware.
• Old lifecycle code, like finished, succeeded, starting, failed methods, are marked as deprecated.
• Tests are updated.
• I bumped a version to 0.27.0-SNAPSHOT, because of deprecations.

[dimafeng]

@LMnet looks great! Thank you!