bump to v2.0.9

Add the ability for a RegisterRenderer to have two parameters passed …

…into its constructor that assign a custom alternates_remplate and register_template to use for these two HTML representations of the Register.

Bump to v2.0.8

Fix several issues. See full commit message:

1) Split rendering an RDF formatted register view into two parts, first generating the RDF graph, and secondly rendering it by serializing it and wrapping it in a response. This allows a specialized renderer to inherit and extend the rdf graph before rendering.
2) Utilize the above new feature to allow a RegisterOfRegisters to inject extra items into the output rdf graph (in this case, the containedItemClass for each subregister)
3) Fix an issue where in some cases the RegisterRenderer rdf view generator would assign a label Literal `rdf:type` instead of `label`.

Large changes in RofR generation.

Use app url_map and view_functions to introspect all endpoints registered on the app, and use the flask test_context to set up internal calls to these endpoints.

Uses the new '_internal' renderer representation format so that the returned object of the endpoint call is the renderer itself.

Use the above object introspection to skip adding RegisterOfRegisters endpoints to RegisterOfRegisters.

Test each endpoint renderer's html, json, and rdf format renders during the creation of the RofR.

Running rofr generation in separate thread is no longer required. Remove the use of Threading from pyldapi setup.

Updated example to reflect setup threading changes.

fixing issues/6

improved default lang

language neg support

fixed profile header selection

used own Media Type choise, not Flask's

handles Accept-Profile header for view