Bypass loopback prevention for deliberate loopbacks (0.9.x)

Sometimes you may want to query a separate local graphite-web instance and if you have configured one or more of your clusters hosts with a hostname of localhost or an IP of 127.x.x.x then this would be the case so with this patch they is treated as a remote host.

0.9.x port of https://github.com/graphite-project/graphite-web/pull/1070
For the host to be queried graphite-web must think it is not local, otherwise it is ignored.  I believe this was loopback prevention so that config can be shared between hosts in a cluster, but sometimes it can be useful to run multiple instances on a single host and have them query one another.