APIView is missing a revision for a recently released package

This might just be a cosmetic issue but I noticed that APIView is showing two API revisions for azservicebus - the baseline, and a "beta", but not the actual releases that exist:

So, I see this:

azservicebus 1.8.2-beta.1:

azservicebus 1.8.0:

BUT, we've released 1.8.1, and that's not showing up. Here's the godoc for it, which only shows up when the release pipeline has completed: https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/messaging/azservicebus@v1.8.1

Interestingly, I was looking at a separate issue and copying/pasting and noticed that, before I released 1.8.1 it _was_ showing up. It almost seems like the version displayed reflects what's in source, including it's version, but doesn't seem to take into account that what's in HEAD isn't the previously released version - it's often incremented almost immediately by our own Github automation.

For instance, this is the revision in the tree: https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/messaging/azservicebus/internal/constants.go

```go
const Version = "v1.8.2-beta.1"
```

Which exactly matches what APIView is currently showing.

Start by comparing APIView's revision discovery with the azservicebus release pipeline and the version source in sdk/messaging/azservicebus/internal/constants.go. Use the reported 1.8.1 pkg.go.dev revision and the current v1.8.2-beta.1 tree revision as reference points; done means APIView shows the recently released package revisions rather than only the current source version.

Written by the indexing model from the issue text.