Log consensus scan URIs, revert BFT logging

[tellary]

Log the scan URIs that formed the BFT consensus for the two reward-accounting reads. Consensus URIs are the f + 1 URIs whose agreement formed the consensus, not every URI that happened to agree with it.

• Expose consensus scan URIs via getRewardAccountingRootHashWithScanUris and getRewardAccountingActivityTotalsWithScanUris return values, and include them in the log messages of CalculateRewardsTrigger and SummarizingMiningRoundTrigger respectively.
• Thread the consensus URIs through the BFT machinery: executeCall and the new private bftCallWithScanUris now return (response, List[Uri]); the *WithScanUris methods surface it while bftCall drops it to preserve the existing callers' signatures.
• Revert the per-call logging customization introduced in SvApp: Do BFT read in CalculateRewardsTrigger, ProcessRewardsTrigger #5768, keeping only the metrics collection and message formatting. All BFT disagreements are now logged uniformly at INFO including those for getRewardAccountingRootHash and getRewardAccountingActivityTotals.
• Drop ConsensusLogConfig since disagreement logging no longer varies per BFT operation.
• Update relevant tests.

Tested locally: TrafficBasedRewardsSvAppTimeBasedIntegrationTest and BftScanConnectionTest pass.

Fixes #5844.

Pull Request Checklist

Cluster Testing

• If a cluster test is required, comment /cluster_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
• If an upgrade test is required, comment /upgrade_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
• If a hard-migration test is required (from the latest release), comment /hdm_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.
• If a logical synchronizer upgrade test is required (from canton-3.5), comment /lsu_test on this PR to request it, and ping someone with access to the DA-internal system to approve it.

PR Guidelines

• Include any change that might be observable by our partners or affect their deployment in the release notes.
• Specify fixed issues with Fixes #n, and mention issues worked on using #n
• Include a screenshot for frontend-related PRs - see README or use your favorite screenshot tool

Merge Guidelines

• Make the git commit message look sensible when squash-merging on GitHub (most likely: just copy your PR description).

[dfordivam]

Thanks, this need some adjustments.

And for the logging added in the triggers we should modify the confirmBftRead in
TrafficBasedRewardsSvAppTimeBasedIntegrationTest.scala, to do assertion of log similar to the loggerFactory.assertEventuallyLogsSeq used in it already.
(also make sure the existing entry.warningMessage assertion in the test passes)

[dfordivam]

We need to revert this to WARN. ie put the disagreementLogLevel back

[dfordivam]

We need to revert this to WARN

[tellary]

we should modify the confirmBftRead

@dfordivam

Ok, I can modify the TrafficBasedRewardsSvAppTimeBasedIntegrationTest to make sure the following logs are emitted:

• From the CalculateRewardsTrigger:

  "Obtained the root-hash for round $round via BFT read from consensus scans: ${scanUris.mkString(", ")}."
  

• From the SummarizingMiningRoundTrigger:

  "Obtained the reward accounting totals for round $round via BFT read from consensus scans: ${scanUris.mkString(", ")}.
  

[tellary]

(also make sure the existing entry.warningMessage assertion in the test passes)

@dfordivam

This assertion is still in the TrafficBasedRewardsSvAppTimeBasedIntegrationTest. The test passes, so the asertion passes.

entry.warningMessage should (include(
  "has a mismatch with confirmations" 
) and include(
  cid.contractId
))

[dfordivam]

Perhaps "BFT read from scans: ..." is better?