Package badges do not exclude broken releases

### Checklist

- [X] I added a descriptive title
- [X] I searched open reports and couldn't find a duplicate

### What happened?

Recently, the Google [protobuf repository](https://github.com/protocolbuffers/protobuf) changed [its versioning scheme](https://protobuf.dev/news/2022-05-06/#python-updates) such that the repo is tagged with, e.g. 22.2, but the specific language implementations in the repo may have a major version prepended. e.g. the Python release is 4.22.2.

During this transition conda-forge released a version 21.2 of the package. This problem was reported and the packages marked broken. Nevertheless, badges report the 21.2 release as the highest available on conda-forge. It doesn't seem right to include broken packages in this calculation.

- https://anaconda.org/conda-forge/protobuf/files?version=21.2
- https://github.com/conda-forge/google-cloud-life-sciences-feedstock/pull/15

I understand that the upstream badge reports 22.2 and that may not have a good, generalizable solution. I'm focusing on the channel badge.

### Conda Info

```shell
active environment : default
active env location : /Users/tpdownes/local/miniconda3/envs/default
shell level : 1
user config file : /Users/tpdownes/.condarc
populated config files : /Users/tpdownes/local/miniconda3/.condarc
/Users/tpdownes/.condarc
conda version : 23.1.0
conda-build version : not installed
python version : 3.10.9.final.0
virtual packages : __archspec=1=x86_64
__osx=13.2.1=0
__unix=0=0
base environment : /Users/tpdownes/local/miniconda3 (writable)
conda av data dir : /Users/tpdownes/local/miniconda3/etc/conda
conda av metadata url : None
channel URLs : https://conda.anaconda.org/conda-forge/osx-64
https://conda.anaconda.org/conda-forge/noarch
package cache : /Users/tpdownes/local/miniconda3/pkgs
/Users/tpdownes/.conda/pkgs
envs directories : /Users/tpdownes/local/miniconda3/envs
/Users/tpdownes/.conda/envs
platform : osx-64
user-agent : conda/23.1.0 requests/2.28.2 CPython/3.10.9 Darwin/22.3.0 OSX/13.2.1
UID:GID : 828971:89939
netrc file : None
offline mode : False
```

### Conda Config

```shell
==> /Users/tpdownes/local/miniconda3/.condarc <==
channels: []

==> /Users/tpdownes/.condarc <==
auto_activate_base: False
changeps1: False
create_default_packages:
- coreutils
default_threads: 5
channel_priority: strict
channels:
- conda-forge
```

### Conda list

_No response_

### Additional Context

_No response_

No implementation file or test is named in the report. Start by tracing how the conda-forge channel badge determines its highest available package version, then inspect how broken releases are represented; done means the badge excludes the broken 21.2 protobuf release while retaining valid versions.

Written by the indexing model from the issue text.