prop224: Refactor connection_ap_handle_onion

That function has two big blocks from an if/else for v2 and v3 address handling. We should refactor this into something cleaner and more modular.

changed milestone to %Tor: unspecified

added 034-removed-20180328 034-triage-20180328 component::core tor/tor milestone::Tor: unspecified parent::23300 priority::medium prop224 severity::normal status::new tor-hs type::defect labels

Trac:
Milestone: Tor: 0.3.2.x-final to Tor: 0.3.3.x-final

Trac:
Status: new to assigned
Owner: N/A to dgoulet

Move 033 ticket I own to 034

Trac:
Milestone: Tor: 0.3.3.x-final to Tor: 0.3.4.x-final

Trac:
Keywords: N/A deleted, 034-triage-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

Trac:
Keywords: N/A deleted, 034-removed-20180328 added

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

Trac:
Milestone: Tor: 0.3.4.x-final to Tor: unspecified

Releasing some old tickets.

Trac:
Owner: dgoulet to N/A

Trac:
Cc: N/A to neel
Owner: N/A to neel

Trac:
Cc: neel to N/A
Owner: neel to N/A

Trac:
Status: assigned to new

moved to tpo/core/tor#23301 (closed)