Make the proxy jump resolver a bit more flexible.

[nightman68]

fix #318.

[tomaswolf]

The list may also need to be reversed. Both your configurations should give a connection

client -> jump3 -> jump2 -> jump1 -> target

but I think they give

client -> jump1 -> jump2 -> jump3 -> target

?

Also: what if host at line 690 is again a chain (multiple hosts separated by commas)? As in the config

Host jump1
  Hostname                    jump1.corp
  Port                        22
  User                        nightman
  ProxyJump                   jump2,jump3
  LogLevel                    QUIET

Host jump2
  HostName                    jump2.dmz.corp
  Port                        22
  User                        nightman
  #ProxyJump                   jump3
  LogLevel                    QUIET

Host jump3
  HostName                    jump3.dmz.corp
  Port                        22
  User                        nightman
  LogLevel                    QUIET

Host host*.dmz.corp
  ProxyJump                   jump1

[nightman68]

1. I fixed the proxy order for "inline" definition - my mistake.
2. The code is now supporting your example configuration above.

[tomaswolf]

Thank you; looks much better. Not sure about the precedence of the lists but we can tackle that issue when it arises.

Could you add tests for this?

[nightman68]

Sorry, I do not have the time at the moment getting familiar with your test suite etc.

[tomaswolf]

Fixed differently via PR #512 (including tests).