feat: add new reconfiguration process

[zepfred]

This pull request introduces a stuck monitor mechanism for the LS phase and a restart process.

1. There is one stuck mechanism based on the unimproved move count of the best solution.
2. The stuck monitor logic employs a technique known as geometric restart, which increases the related metric exponentially.
3. The restart process is executed by the LS every time the solver is stuck. Currently, the process simply restores the last best solution and "restarts" the search.

[triceo]

First round of review is in.

My most general comment is: we need a different name for "reconfiguration". I know that the papers use this word, but we cannot. We already have "configuration", and using "reconfiguration" would be confusing - the "configuration" in "reconfiguration" has nothing to do with solver configuration.

Reheating? Restart? Refresh? Reboot? Let's discuss.

[triceo]

Another concern: we only support LA (and DLAS). But shouldn't we support simulated annealing too? In SA, the process is actually called reheating, and is well researched as far as I know.

For the record: I don't much care for SA, because it is hard to configure and therefore not much useful. But if we don't support reheating the SA, it should be a conscious decision, and not just something we forgot to do.

[triceo]

Next round of comments.