Change DB structure for optical throughput

Summary

Currently we are creating and processing distinct DB table with version information, and only for the optical throughput (in atmospheric calibrations this version control table is not used at all).

Work with this table can be found in:

• appropriate container calibpipe/database/adapter/database_containers/version_control.py
• handling of this table in calibpipe/tools/throughput_calibrator.py
• tests in calibpipe/tests/unittests/throughput/test_throughput_calibration.py.

Now, as we have implemented common reference metadata, I believe this version control table is deprecated, and we should use one common schema for all our pipelines.

What is the expected correct behavior?

I propose to completely exclude this table from optical throughput DB processing, and store version value in the reference metadata table. To do this:

• Refactor throughput_calibrator to:
  • don't use the version_control schema at all.
  • add functionality to upload common metadata tables to our DB.
• Rewrite tests that are involved into this deprecated version_control schema.

Relevant logs and/or screenshots