Traffic-Based App Rewards: Integrate the Reward Computation Trigger with the necessary daml contracts

[adetokunbo]

Contributes to #4383
Stacked on #5060

This integrates the RewardComputationTrigger with the Daml contracts from which it obtains the values it uses in its calculations

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 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]

We have an issue here, the round checked here will actually never get skipped and will block the trigger to process further rounds.
I modified my integ test to add, and then remove rewardConfig from amulet config, and confirmed that trigger gets stuck.
We have to make sure we skip here as the mainnet has been running reward computation, and that will cause latestCompleteO to be Some even in absence of rewardConfig.

[dfordivam]

Actually using earliestRoundWithRewardConfig(Some roundNumber, latestCompleteO) here should work right?
Perhaps we could re-structure the code such that finding the correct round with config is done at both places with single generalized API

[dfordivam]

Based on response by Simon yesterday on the doc, we dont need to handle this scenario right now. So lets make sure we truncate the tables on feature branch