tor_socksproto::Error HasKind fix two delegations

We should not generally explicitly specify a kind for errors which contain a more detailed error which itself has a kind. Stating the kind literally is a latent bug, which becomes a real bug if the contained type's kind changes or starts to vary.

(There may be exceptions to this principle but this isn't one of them.)