The right path for your module, according to your go.mod file, begins with gopkg.in/sohlich/elogrus. https://pkg.go.dev/gopkg.in/sohlich/elogrus.v7 works fine.
The path starting with github.com is from before you had a go.mod file, and shouldn't be used.
If you'd like, we can remove it.

Not my package, so I cant make a decision on its removal.

Would it be viable for packages that have a common source repository to be linked together somehow to prevent this in the future? Or some other form of detection of module path change? Its likely a rare edge case, but still infuriating if you are an outside user.

We do detect and reject modules whose path does not match the path in the go.mod file. The problem is that the github package doesn't have a go.mod file to check with. pkg.go.dev only knows about module zip files (except, as a heuristic, we try to link source to the originating repo), so there's no way to tell that the github path is "bad" here.

Filed sohlich/elogrus#35.

Assuming nothing else needs to be taken care of then as it is now tracked in that ticket, closing this one.