ce19db6 Store pungi_config_dump in database.

Authored and Committed by jkaluza 4 years ago
    Store pungi_config_dump in database.
    
    To be able to rebuild production composes in the future, it is
    needed to store the full Pungi configuration dump in the ODCS
    database.
    
    This commit does following to implement it:
    
    - New `pungi_config_dump` column is added to database.
    - The API returns `pungi_config_dump`, but only in case when
      single ODCS compose is returned. In case multiple composes are
      queried, this field is not returned to keep the response small.
    - The `pungi_config_dump` is also not sent in UMB or fedora messages.
    - The `pungi_config_dump` is stored only for `production` composes.
    - In case the config dump cannot be found in generated compose,
      the compose is marked as `failed`. It means every `production`
      compose must have the config dump stored in the database.
    
        
file modified
+5 -0
file modified
+10 -2
file modified
+20 -0
file modified
+1 -1
file modified
+9 -6
file modified
+4 -2
file modified
+11 -0
file modified
+2 -0