Fix mutual close

[marsella]

Closes #337

Before, the merchant's close() function called finalize_mutual_close. Now, the merchant's watcher calls it.

The most substantial change here is an addition of MutualCloseBalances to the merchant database. The merchant watcher cannot tell from the contract itself what the final mutual close balances are, so we need to persist them via the database instead. These changes include

• updating the database schema to include this optional field (sqlx-data.json is the generated file)
• updating the database Rust type to include the field
• adding a getter and setter for the field for a specific channel id

Observation: the getters for each field of the database are a bit clumsy -- they're all identical except for the item being queried. Would it be better to have a single getter for the whole row, and have the caller pull out the field relevant to them?

Testing: I think this scenario is not currently caught by the e2e testing infrastructure. Should determine whether it is and either fix it in this PR or make a new issue + PR to address it.

[gijsvl]

In regard to your comments:

• I think we should take your suggestion and check if this is covered by e2e testing, we can't keep postponing testing to new PRs in my opinion, just because the pile of testing we still have to do just grows, it's not making it easier.
• The separate getters are fine as long as we don't do multiple getters just one after another... Every query takes time, we should make sure we make 1 query at a time and if we can combine queries we should do so. But querying everything at once if it is not necessary might also be unnecessary.

[marsella]

Testing comments remain important, but we've discussed and it seems like they will be better addressed by a significant update to the testing infrastructure, rather than trying to jerry-rig the script we currently have. See #69 for the plan to address this issue.

Force-push to rebase to main and fix a compile issue with the CI.