[#3] Adding session information

Creating session and storing information in it.
Modular app using flask Blueprints

In the need to separate logic, code and administration, flask offers
Blueprints.

I changed only part of it and seems to be working... gives more
flexibility and helps with the routing.
Route was broken
Remove testing print instructions
Making homepage work again

Moved old views to another blueprint and got rid of a lot of dummy routes
Adding a main application concept.

Now that we are using blueprints, we should have a main `application` object.
This is living under `labmanager/application.py`. The goal of this app file
is to have a main object representing the whole application. Specially the
public parts.

Instead of always importing everything, we can choose only some functions where
needed.
Moving login bits of LTI to a LTI focused file
Adding a SCORM package file to build the blueprint
Use the new blueprint
Change configs name and removed import
Split admin panels into category files

Adding a little bit more structure to the files and code. This way it is
easy to know where all the admin views related to some category are. And well,
we don't have a huge file filled with classes.
Adding default attributes to admin panels
Removing unused routes
Empty models files
Splitting model files into different models.
Dont allow access to new panels
[#3] Adding session information

Creating session and storing information in it.
Modular app using flask Blueprints

In the need to separate logic, code and administration, flask offers
Blueprints.

I changed only part of it and seems to be working... gives more
flexibility and helps with the routing.
Route was broken
Remove testing print instructions