Added builder for timeouts in JdbcDatabaseContainer (#715)

[StefanHufschmidt]

Added builder functionality for timeouts in JdbcDatabaseContainer to improve usability for e.g. MS SQL Server image which needs much more time to start up.

I have seen the workaround with override from @vpavic at #715 and made it configurable by builder pattern to increase usability.

@kiview or @rnorth may take a look at it?

[kiview]

Seems like a pretty good idea and it's just a small change.

On the other hand, see this comment by @vpavic:

Just to note, providing custom timeout value(s) isn't a problem by itself, however when you do that in multiple different project it becomes a bit annoying, so my hope was this issue would result in a more sane default in Testcontainers.

So maybe MSSQLServerContainer should also have a higher timeout by default?

[kiview]

OracleContainer is overriding this method, so this PR should also change OracleContainer to use fluent-setter to set it's default value.

[StefanHufschmidt]

Initially I wanted to put setting the default timeouts into the configure-method but this would override values which where set by the user.
Now it happens inside the specific constructor so the user can still change it afterwards.
I've added a deprecation annotation to the related getter to make the builder methods more popular and to be able to remove those methods in future, we could use the fields directly then.