Package structure and imports

Since the ToolBox already includes a lot of code I believe make sense to make a proper package out of it. The benefit is:

• Easy installation for users.
• Collaborators understand better how the code is organized and where certain contributions should go.

Other than that, the namespaces of individual sub-packages could be organized in a way that is similar to other third-party python packages. Next to the more standardized use it also helps to foresee and avoid problematic naming and import behavior.

A concrete example: the module Load imports the module bunch_pattern, which in turn imports mnemonics from the module Load not yet known. This only works in the case, when absolute self references are used (from Toolbox. .. import ) and that name remains unchanged.

In the branch DevelopmentRG I started to work with a package structure. If wanted this could be merged into the master. The implemented hierarchy can of course be debated.