Stop checking if ri->address is an IP

since router_parse_entry_from_string() already checks whether
!tor_inet_aton(router->address, &in)

(And no need to print address, since router_describe does that.)
stop passing "address" around the directory_initiate_command* funcs

since it was always just the string version of "addr" anyway
use router->addr for log messages and controller events

(rather than router->address)
use me->addr when adding our address to our exit policy

(rather than me->address)
stop setting, or using, router->address

resolves ticket 5528.
eventdns.c: survive broken resolv.conf files

If you had a resolv.conf file with a nameserver line containing no
nameserver IP, we would crash.  That's not terrible, but it's not
desirable.

Fixes bug 8788; bugfix on 0.1.1.23.  Libevent already has this fix.
Warn if ports are specified in {Socks,Dir}Policy

We have ignored any ports listed here since 80365b989 (0.0.7rc1),
but we didn't warn the user that we were ignoring them.  This patch
adds a warning if you put explicit ports in any of the options
{Socks,Dir}Policy or AuthDir{Reject,Invalid,BadDir,BadExit}.  It
also adjusts the manpage to say that ports are ignored.

Fixes ticket 11108.
Merge remote-tracking branch 'public/bug8788'
Merge remote-tracking branch 'arma/ticket5528'

Conflicts:
	src/or/router.c
	src/test/test_dir.c
PredictedCircsRelevanceTime: limit how long we predict a port will be used

By default, after you've made a connection to port XYZ, we assume
you might still want to have an exit ready to connect to XYZ for one
hour. This patch lets you lower that interval.

Implements ticket 91
Added Documentation for PredictedCircsRelevanceTime config file argument.
Added max value to PredictedCircsRelevanceTime.
More correctly documented PredictedCircsRelevanceTime in tor.1.txt
Fixed spacing.
Lower the maximum for PrecictedCircsRelevanceTime to one hour
Fix wide lines.
Merge branch 'ticket9176_squashed'

Conflicts:
	doc/tor.1.txt
Rename PredictedCircsRelevanceTime->PredictedPortsRelevanceTime

All circuits are predictive; it's the ports that are expiring here.
Fix whitespace errors, all of them mine.
Correct the URL in the "a relay on win95???" message

This is a fix for 9393; it's not a bugfix on any Tor version per se,
but rather on whatever Tor version was current when we reorganized the
wiki.