Reduce logging to main output in build and add testbed log archive

[peterbroadhurst]

Proposed changes

• Move back to default logger, so we capture firefly-signer and zeto logs too
  • Note Do not force logrus LogLevel on first log line hyperledger-labs/zeto#103 to fix the reason we made the change before
• Move all testbed logs to file based testbed.*.log
  • To massively reduce the overload of logging on the github build output
• Add github action task to upload logs

Note I attempted lots of ways to get log4j2 to do rolling file based logging, and after much frustration and reading of examples I gave up - sorry 🙇

... some bundle of code I gave up on, with multiple different approached embedded, none of which either:

• switched off console logging
• made anything appear in the files it started creating

        if (logConfig.output().equals("file") && logConfig.file() != null) {
            ConfigurationBuilder<BuiltConfiguration> builder = ConfigurationBuilderFactory.newConfigurationBuilder();
            builder.setStatusLevel(level);
            builder.setConfigurationName("DefaultLogger");
            var triggeringPolicy = builder.newComponent("Policies")
                    .addComponent(builder.newComponent("CronTriggeringPolicy").addAttribute("schedule", "0 0 0 * * ?"))
                    .addComponent(builder.newComponent("SizeBasedTriggeringPolicy").addAttribute("size", "100M"));
            LayoutComponentBuilder layoutBuilder = builder.newLayout("PatternLayout")
                    .addAttribute("pattern", "%d [%t] %-5level: %msg%n");
            var appenderBuilder = builder.newAppender("rolling", "RollingFile")
                    .addAttribute("fileName", "%s.jlog".formatted(logConfig.file().filename()))
                    .addAttribute("filePattern", "%s.jlog-%%d{MM-dd-yy}.log.gz".formatted(logConfig.file().filename()))
                    .add(layoutBuilder)
                    .addComponent(triggeringPolicy);
            builder.add(appenderBuilder);
            builder.add( builder.newRootLogger( level )
                    .add( builder.newAppenderRef( "rolling" ) ) );
            Configurator.reconfigure(builder.build());
        }

        final LoggerContext ctx = (LoggerContext) LogManager.getContext(false);
        final Configuration config = ctx.getConfiguration();
        for (var appender :  config.getRootLogger().getAppenderRefs()) {
            config.getRootLogger().removeAppender(appender.getRef());
        }
        ctx.updateLoggers();

        Configurator.setAllLevels("io.kaleido.paladin", level);

[awrichar]

is this needed?

[peterbroadhurst]

Yeah - I believe so, otherwise on failure (when we need the logs most), the step is skipped