Htagweb

Add another new runner "AppServer", which is fully compatible with old classics ones : WebServer/WebServerWS/WebHTTP/WebWS.
Except: tags should use "self.root.state" to maintain a state (because F5 will destroy/recreate instances)

And yes, there is no "0.6.0" (because, lot of troubles when ci/cd/crafting whl for pypi) ;-)

**Full Changelog**: https://github.com/manatlan/htagweb/compare/v0.5.0...v0.7.0

* the htagserver runner, works as others htag classical runners (can handle a main tag for its '/' path, have a .run() method, can use add_route )
* an example of an oauth2 flow (google), using authlib, and inner runners (WebServer, WebServerWS & HTagServer)
* the one liner "python3 -m htagweb" accept a parameter 'fqn' (ex: 'main:App'), to define a htag class for its "/" page.

**Full Changelog**: https://github.com/manatlan/htagweb/compare/v0.4.3...v0.5.0

WebServer & WebServerWS don't create trailing vars in session (ht_create/ht_interact)

* WebServer & WebServerWS are now compatible with htagweb'fqn .... in place of "module.App" you can use "module:App". More compliant.
* htagweb try to clear the imports of the class, if not defined, to avoir cluttering statics spaces

Just some cosmetics changes on HtagServer.IndexApp ...
it's more beautiful

htagweb provided WebServer & WebServerWS, which are "robust" web servers for exposing htag's app on the web.

Now, it provides a different beast "HtagServer" (you can run it, by default, in command line `python3 -m htagweb`). Which will expose the current working directory in a http/ws server. It doesn't work as WebServer & WebServerWS, or classicals htag runners. It's a completly new concept. But it provides all the highends features of web/htag. I'm exploring that ;-)