fix: deterministic cluster time

[wdconinc]

Briefly, what does this PR introduce?

This PR makes the cluster time deterministic, and not based on the whim of which hit happens to be first. It defines the cluster time as the energy-weighted average of all hit times.

This is not the only deterministic choice here (earliest hit is another).

What kind of change does this PR introduce?

• Bug fix (issue: cluster time depends on hit ordering)
• New feature (issue #__)
• Documentation update
• Other: __

Please check if this PR fulfills the following:

• Tests for the changes have been added
• Documentation has been added / updated
• Changes have been communicated to collaborators

Does this PR introduce breaking changes? What changes might users need to make to their code?

No.

Does this PR change default behavior?

No.

[github-actions]

Capybara summary for PR 1584

• rec_dis_10x100_minQ2=0_craterlake
• rec_dis_10x100_minQ2=1000_craterlake_tracking_only
• rec_dis_18x275_minQ2=0_craterlake
• rec_dis_18x275_minQ2=1000_craterlake
• rec_dis_5x41_minQ2=0_craterlake
• rec_e_1GeV_20GeV_craterlake
• rec_pi_1GeV_20GeV_craterlake
  ^{_{Last updated 2024-08-19T16:07-04:00 0034d12}}

[ruse-traveler]

🙏 Very nice!

This looks good to me, though I'm curious about the pros-and-cons of using the time-weighted time vs. earliest.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[ruse-traveler]

LGTM!