It's confusing that a PrimaryServerSelector instance does not behave identically to a ReadPreferenceServerSelector with a primary read preference. The latter treats clusters with a direct connection mode specially, while the former does not. To remove this confusion, we should deprecate PrimaryServerSelector and add a new WritableServerSelector that works the same. In others, a class rename that doesn't break compatibility.