Reset lock documents on startup (#211)

In the situation the services crashes or gets killed while a lock is
being held, it would startup into an incorrect state. On startup, the
lock documents are resetted to recover from such a case.

This can be problematic when many services are deployed, because it
would reset all documents right now. This will be addressed in a
future change and for the currently foreseeable future, there will be
only one instance.

modules/search-provision/src/main/scala/io/renku/search/provision/Microservice.scala

@@ -44,8 +44,12 @@ object Microservice extends IOApp:
           logger
             .warn(s"There were ${migrateResult.migrationsSkipped} skipped migrations!")
         )
-        // this is only safe for a single provisioning service
-        _ <- services.resetLockDocuments
+        // this is really only safe for a single provisioning service,
+        // but for the immediate future that is the situation. So do
+        // this to recover from crashes during a lock is held
+        _ <- services.resetLockDocuments.handleErrorWith { ex =>
+          logger.warn(s"Resetting locks on start failed", ex)
+        }
         registryBuilder = CollectorRegistryBuilder[IO].withJVMMetrics
           .add(RedisMetrics.queueSizeGauge)
           .add(RedisMetrics.unprocessedGauge)