Prevent Go modules from overwriting direct dependency version due to indirect import of same dependency

Question

I have a Go mods project with the following dependencies:

require (
    github.com/owner1/projectA v1.0.0
    github.com/owner2/projectB v0.5.0
)