Ledger Api Server logging: Lower selected logger.info to logger.debug

[oliverse-da]

StandaloneIndexerServer:

-                  () => logger.info("successfully finished processing state updates")))(DEC)
+                  () => logger.debug("successfully finished processing state updates")))(DEC)
..
-    logger.info("Started Indexer Server")
+    logger.debug("Started Indexer Server")

StandaloneIndexServer:

-    logger.info("Initialized index server version {} with ledger-id = {}, port = {}, dar file = {}",
+    logger.debug("Initialized index server version {} with ledger-id = {}, port = {}, dar file = {}",
...
-    logger.info("Started Index Server")
+    logger.debug("Started Index Server")

JdbcIndexer:

-          logger.info(s"Initializing ledger with id: ${ledgerId.unwrap}")
+          logger.debug(s"Initializing ledger with id: ${ledgerId.unwrap}")

ReadOnlySqlLedger:

-    logger.info(s"Found existing ledger with id: ${foundLedgerId.unwrap}")
+    logger.debug(s"Found existing ledger with id: ${foundLedgerId.unwrap}")

FlywayMigrations:

-      logger.info(s"running Flyway migration..")
+      logger.debug(s"running Flyway migration..")
...
-      logger.info(s"Flyway schema migration finished successfully applying ${stepsTaken} steps.")
+      logger.debug(s"Flyway schema migration finished successfully applying ${stepsTaken} steps.")

LedgerApiServer:

        logger.info("Starting plainText server")
...
        logger.info("Starting TLS server")
...
      logger.info(s"listening on ${address.getOrElse("localhost")}:${grpcServer.getPort}")

[oliverse-da]

logback setting workaround

[oliverse-da]

Put in place canton work-around - closing as we discussed having logging useful for production rather than testing is the way to go.