fix(suspect commits): Use release date as the upper bound for SCM-based commit filtering

[shashjar]

Fixes #78300.

When a group has a first_release, use min(release_date, group.first_seen) as the upper bound for suspect commit filtering, instead of group.first_seen alone. This prevents flagging commits that were landed after the release was built, meaning that those commits could not possibly have caused the issue and therefore should not be identified as suspect commits. This logic falls back to group.first_seen when no release is available/found (which matches existing behavior).

The group_first_seen parameter in find_commit_context_for_event_all_frames is renamed to commit_date_max to reflect the updated semantics.