improve plugin registration sanity checks
new plugin TE_ASSET

usage:
{ASSET:some-image.png} => browser relative path in either the current
template or the base template. By default the jail_to_template_path option
is enforced, but the force_tpl_extension is not because this directive
is supposed to be used to allow overriding of stylesheets,
images, ... in sub templates