Require new ParseXS version and EU::Typemaps
Require event newer ParseXS
Allow storing/fetching of an xs_type from Typemap objs
Generate typemap block on demand
embedded typemap output test
Start implementing auto-generated class typemaps
Generate inlined typemaps for XS++ classes

This will make xspp generate a block like the following for each of the
classes* that are found in XS++ interface code.

  TYPEMAP: <<END
  TYPEMAP
  YourClass*   O_OBJECT
  END

And additionally, if you don't define INPUT/OUTPUT for O_OBJECT
yourself, it'll include the de-facto standard ptr-in-IV typemap for
O_OBJECT.

Also adds plenty of additional documentation for typemaps.

Adds tests for the generated inline-typemaps.

Does not yet handle non-simple XS++-type-mapped class definitions.

Needs review and much more importantly, real-world testing.

* "Each" means that this includes any base classes that you mention in
  the XS++ code.
Ignore duplicate typemaps
Support xs_type in all Typemap subclasses

This allows me to ditch the superfluous simplexs.pm subclass.
TODO/FIXME shuffling
class typemaps generally no longer needed
git ignorance for build byproducts
Ditch superfluous maps
Adapt new %alias tests to work with generated typemaps
Move file preamble code all in the same place.
Do not test preamble code in tests.
Make the default OUTPUT typemap work both in a constructor and in a normal method.

Implemented by using an XS++-specific macro which is defined differently
for constructors and normal methods; there is no way to solve this just
with ExtUtils::ParseXS (would require a special constructor annotation,
since constructors can be renamed).
Remove duplicate assignment.
Simplify add_weak_typemap_for_type.

Instead of looking for existing typemaps with a matching type,
just add weak typemaps at the end of the list.
Small refactoring.