[WIP] creating timezones from VTIMEZONE components

I'd like to run this by you before it is ready, so everybody can voice their conceptual problems with this approach early. Once this is ready it should close #44.

TZIDs known to the TZDB, are left alone and data from the TZDB is used as before. Every TZ is only created once and registered in a global timezone dict.

Some caveats:
 * we are currently relying (especially the tests) on pytz internals
 * this only works when VTIMEZONE components come before DATE-TIME components that make use of them (while this seems to be the standard way to generate icalendars, there is no word about this in the RFC). To circumvent this, we would probably need some architectural changes, like  two rounds of parsing.
 * tz creation feels a bit brute-forced into cal.py, but there are so many exceptions in from_ical() already, that I don't feel  too guilty about introducing one more.


TODO
--------

* [ ] check for the edge case of DST moving a timezone over the date line
* [ ] some rounding issues (see to_tz() )
* [ ] more tests
I agree, that this is kind of magic, I had to read [this](http://www.jeffknupp.com/blog/2013/12/28/improve-your-python-metaclasses-and-dynamic-classes-with-type/) to understand how it works. But this is actually [how pytz's timezones are made](http://bazaar.launchpad.net/~stub/pytz/devel/view/head:/src/pytz/tzfile.py#L120), too.