Bodhi update (from side tags) failed for the wrong reason

[sentry]

It could happen that a latest stable build does not exist for a package when trying to create a bodhi update from side tags. In this case, it was the packit package for the stable tag epel10.3-testing-candidate.

The update shouldn't stop with an error; instead, it should just log it as a warning, since the build can still be found in the side tag where we want the update to happen.

Sentry Issue: PCKT-002-PACKIT-SERVICE-B6F

TypeError: 'NoneType' object is not subscriptable
(7 additional frame(s) were not displayed)
...
  File "packit_service/worker/handlers/bodhi.py", line 268, in _get_or_create_bodhi_update_group_model
    str(b) for b in sidetag.get_builds_suitable_for_update(dependencies)
  File "packit_service/worker/helpers/sidetag.py", line 49, in get_builds_suitable_for_update
    latest_stable_nvr = self.koji_helper.get_latest_stable_nvr(
  File "packit/utils/koji_helper.py", line 220, in get_latest_stable_nvr
    build = self.get_latest_stable_build(
  File "packit/utils/koji_helper.py", line 196, in get_latest_stable_build
    return max(
  File "packit/utils/koji_helper.py", line 198, in <lambda>
    key=lambda b: NEVR.from_string(b["nvr"]),

[nforro]

since the build can still be found in the side tag where we want the update to happen.

No, this is incorrect. We are figuring out if a build that's in the sidetag is or is not already in some Bodhi update. If it is, we know it has been tagged into the sidetag only to satisfy a dependency and we won't add it to the update. If there is an error when searching for the build, it simply means that it can't be in any existing update and we can safely add it.