Fix a bug in deciding local GTM proxy while adding a new datanode master
Fix a bug in deciding local GTM proxy while adding a new datanode master

We should be looking at the hostname and not the datanode name while picking up
a local GTM proxy

postmind-net/postgres-xl,snaga/postgres-xl,kmjungersen/PostgresXL,postmind-net/postgres-xl,kmjungersen/PostgresXL,arcivanov/postgres-xl,arcivanov/postgres-xl,postmind-net/postgres-xl,arcivanov/postgres-xl,kmjungersen/PostgresXL,postmind-net/postgres-xl,snaga/postgres-xl,arcivanov/postgres-xl,snaga/postgres-xl,snaga/postgres-xl,kmjungersen/PostgresXL,arcivanov/postgres-xl,postmind-net/postgres-xl,kmjungersen/PostgresXL,arcivanov/postgres-xl,snaga/postgres-xl