💡 Feature suggestion for Runboat: persist database across builds of the same PR/branch

[Yusuke1998]

It would be extremely helpful if Runboat allowed reusing the database from a previous build when creating a new build for the same pull request or branch. This would greatly simplify workflows involving complex configurations and large datasets, especially when relying on data modules or fixtures is not feasible.
For instance, if a PR build involves setting up multiple modules with specific data (e.g., commission rules, large catalogs), updating that PR with a fix currently triggers a fresh build that requires redoing all configurations from scratch. This is time-consuming and makes incremental validation harder.
Moreover, even attempting to export the database from a previous build and import it into the new one doesn’t seem to work reliably. Runboat appears to reject the import, even when the correct master password is provided.
Adding support to persist or restore the database from a previous build of the same PR/branch would be a major improvement for teams working with iterative builds and non-trivial data setups.