Adding primary key and DB container for metadata for optical throughput

Summary

I suggest using an auto-incremented value named id as the primary key for each row of the optical efficiency data table.

New realisation of Optical Throughput DB is the next:

• each record of optical throughput data table was obtained by one particular activity (optical throughput calculation) and for one process (observation), but each process can have several instrument related records for different telescopes, subarray etc.

What is the expected correct behavior?

• Implement primary key named id as auto incremented value for appropriate optical throughput DB containers in the calibpipe/database/adapter/database_containers
• So far all these meta tables are implemented in the ctapipe as different classes, which can be represented as dictionaries or hdf5 tables. We should decide how to re-use them in our purposes.

Relevant logs and/or screenshots

Explanation of Reference Metadata fields can be found in this Issue #135 (closed)

DB Schema, still need to decide which fields we will preserve in the main datatable, as far as most of them are repeated in the metadata.