Terminate gracefully

The current way of terminating Foundry is to drop all resources at the end of run_node function.
Since we didn't care about the order of drop, sometimes Foundry panics in the termination process since other resources are dropped without expectation.
In the worst case, the database can be corrupted in the termination process.

Start by tracing the termination path at the end of run_node, including how resources are dropped and how the database participates. Determine the required drop order and inspect existing shutdown-related tests or entry points if present. Done means termination completes without panics and does not risk database corruption.

Written by the indexing model from the issue text.