Single onion service client side issue

Keeping this confidential for now until we can sort it out and confirm I'm not delusional :).

While doing some spelunking into the arti HS code for congestion control work, I've discovered this:

let hs_hops = if desc.is_single_onion_service() { => usize
   1
} else {
   HOPS
};

... which is legit EXCEPT that this piece of code is client side from the intro_rend_connect() function in connect.rs which from what I can tell is only client side.

Single onion service is one hop from the service side as in relinquishing anonymity but client side keeps it with the 3 hops.

If I'm right, a BIG IF, maybe we could think of some code design to ensure anonymity at all time on client side?

@gabi-250 @nickm @Diziet