This reverts commit fb4d5885:

"For one, as Michael already responded, many builds (local, Gerrit/Jenkins,
other tinderboxes) now fail UITest_writerperfect_epubexport with what looks like
random 'raise DialogNotClosedException()'.  Gut feeling is that it's way more
than used to fail UITest_writerperfect_epubexport with a deadlock."
(<https://lists.freedesktop.org/archives/libreoffice/2018-February/079494.html>
"Re: UITest_writerperfect_epubexport hang (only sometimes)")  For example,
<https://gerrit.libreoffice.org/#/c/50070/> "tdf#115853: save current custom
property when adding line" Jenkins linux_clang_dbgutil_64 now failed twice in a
row with what looks like random "raise DialogNotClosedException()" failures in
UITest_writerperfect_epubexport.

And for another:  "As long as its unclear what the underlying problem is, what
benefit does it have to add a timeout failure path in the test?  Without the
added timeout, a local failed test will be ready to be inspected (and moggi now
gave suggestions what exactly to inspect in another mail in this thread).  And
failed tests on the tinderboxes will eventually time out either way."
(<https://lists.freedesktop.org/archives/libreoffice/2018-February/079491.html>
"Re: UITest_writerperfect_epubexport hang (only sometimes)")

Change-Id: I36db7526b68a1cf6be596aa82c57095e4067c150
Reviewed-on: https://gerrit.libreoffice.org/50080Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>