use iri_setport instead of reaching into the struct iri

iri: add iri_setport() takes a string because the internals of telescope makes it easier to use if a string.

remove phos; now unused phos was an attempt at building a gemini client/server library. It didn't went as I expected, mostly because it's such a simple protocol... Anyway, the only use in telescope was for the uri module, which has already been replaced with the built-in iri. Which still sucks (and despite the name, can still only handle URIs) but it's hopefully better. The APIs are better.

convert the remainig uses of phos_uri to the iri API

net: don't need a uri, just host and port fields While here, make 'em dinamically allocated.

move cwd to fs.c

update copyright date for emoji.txt

apply load-url-use-heuristic for command line arguments too This semplifies a bit the handling. humanify_url() now takes the base URL which we can then use when not using the heuristics. Command-line arguments now take an implicit base of <file://$PWD/> when the heuristics are disabled, so that foo.gmi resolves to the local file even without <./>. See github issue #10.

iritest: one more test, just in case It stemmed from my misuse of iri_parse(). There's nothing wrong in the parser (that I found at least), but one more test won't harm.

convert humanify_url to iri APIs

convert ir_select_reply() to iri

add missing include

fix iritest CFLAGS; add iritest to TESTS

sync changelog

add the up, root and home commands These navigates respectively one level up in the path hierarchy, to the root directory and to the "home". The home is considered to be the first path component in the form of ~username. `home' is yet to be implemented.