Handle interruption for BerkeleyJE backend

[mad]

Fixes #2120

---

Thank you for contributing to JanusGraph!

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

For all changes:

• Is there an issue associated with this PR? Is it referenced in the commit message?
• Does your PR body contain #xyz where xyz is the issue number you are trying to resolve?
• Has your PR been rebased against the latest commit within the target branch (typically master)?
• Is your initial contribution a single, squashed commit?

For code changes:

• Have you written and/or updated unit tests to verify your changes?
• If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
• If applicable, have you updated the LICENSE.txt file, including the main LICENSE.txt file in the root of this repository?
• If applicable, have you updated the NOTICE.txt file, including the main NOTICE.txt file found in the root of this repository?

For documentation related changes:

• Have you ensured that format looks appropriate for the output in which it is rendered?

[porunov]

I verified that the added test BerkeleyInterruptionTest passes (when enabled).
The refactoring changes looks good to me, but I didn't dive into the logic itself because I'm not using BerkeleyJE.
LGTM. Thank you @mad !

[janusgraph-automations]

💚 All backports created successfully

Status	Branch	Result
✅	v0.6

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

[janusgraph-automations]

💚 All backports created successfully

Status	Branch	Result
✅	v0.6

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

[porunov]

@mad @li-boxuan apparently TP tests for BerkeleyJE were not executed in this PR, but they are failing now.
The problem is that simply adding [tp-tests] to the commit message and not to the PR name itself isn't enough to trigger TP tests in the PR anymore. We should probably fix it in GitHub actions, but I noticed that for a PR to trigger TP tests not only the commit message should include [tp-tests], but also a PR name itself should include [tp-tests].

@li-boxuan after merging this PR (commit cdea0d7 ) the master branch is now failing due to failed BerkeleyJE TP tests. We should either revert that commit or fix the bugs.

[li-boxuan]

Revert PR: #4037

[li-boxuan]

@mad I reverted this PR due to its failure for tp-tests. It would be great if you could reopen the PR after fixing it, thank you!

[tien]

Would be great to have this fix available soon. Got a fright having the server crashed today 😅