New node tracing system support

[johnalotoski]

This PR changes the default tracing system to the new tracing system and implements support for this where needed:

For Cardano-lib:

• Per environment attributes of nodeConfig and nodeConfigBp now are populated with new tracing system configuration
• New per environment attributes of nodeConfigLegacy and nodeConfigBpLegacy are available until the legacy tracing system is removed from node
• New per environment attribute of tracerConfig is available, for use with cardano-tracer
• New exposed top level attributes include defaultLogConfigLegacy and defaultTracerConfig
• The mkConfigHtml function has been updated to include legacy configuration files, $ENV-config-legacy.json and $ENV-config-bp-legacy.json, and a new tracer config file, $ENV-tracer-config.json

For generic log config:

• cardano-lib/generic-log-config.nix now holds new tracing system default config instead of legacy config

For generic tracing config:

• cardano-lib/generic-tracer-config.nix now holds tracing system default config

For testnet template config:

• cardano-lib/testnet-template/config.json now holds new tracing system template config instead of legacy config

For legacy generic log config:

• cardano-lib/generic-log-config-legacy.nix now holds legacy tracing system default config

For legacy testnet template config:

• cardano-lib/testnet-template/config-legacy.json now holds legacy tracing system template config

Other changes include:

• The environment attribute usePeersFromLedgerAfterSlot has been renamed to useLedgerAfterSlot for consistency with the topology file key value it sets. A corresponding change has been made in the nixos cardano-node service.
• The default auto-generated topology file name has been changed from topology.yaml to topology.json to reflect json contents.
• Nixpkgs was bumped to a recent version and breakage changes were resolved with overlay adjustments for bomutils and nixWrapped util.

[mgmeier]

LGTM minus the one non-existing config option.

I think it would be a nice touch to add comments everywhere, as the nix svc is meant to be a generic one. Also I hope it clarifies that settings on cardano-tracer do NOT affect the message detail or filtering of what the forwarding client (in this case, the Node) is configured to emit (in the Node config).