Throughput tool refactoring

Description

I slightly changed the way how this tool works. Now it doesn't have two options - write to DB or write to tables. Instead, now throughput_tool is writing to DB together with appropriate metadata, and then it writes to the ecsv tables, each row correspond to one record in DB, each file corresponds to one metadata table.

If such approach is satisfactory, I will add new tests to check table creation.

Commits

• Code style improvement according to pylint

• Changed tests accordingly

• Add metadata upload and tables creation

• Refactor of database input arguments

• Deleted version compatibility checks

Related Issue

Closes #145 (closed), #131 (closed), #159 (closed)

Partially adresses #152

How Has This Been Tested?

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.