Storing ecsv files in the DB

Summary

Currently there is no functionality that gets an ecsv file (or astropy table) and stores it in the DB. (On the other hand the opposite exists, i.e. returning a DB table as a qtable). The atmospheric calibration produces 3 types of ecsv files (Atmospheric profile, Rayleigh scattering extinction, molecular density profile) that can be reference or tailored. Probably more will be added in the future.

What is the expected correct behavior?

We have the insert_row_in_database that gets as an argument an sqalchemy table and the upload_data that gets a container. One of the 2 should be generalised in order to receive a QTable or ecsv file. Alternatively, we can create containers by reading the ecsv files but this should be generalised, and not be done during the creation of each individual profile.