pyaerocom/aeroval output should use aerovaldb-locking for all output

[heikoklein]

Is your feature request related to a problem? Please describe.
To make parallelization of pyaeroval-runs possible, the output of the different runs should not conflict with each other. AerovalDb has now locking implemented and pyaeroval should therefore use this locking feature in a fine-grained manner, e.g. log for as short as possible (but not so often that writes are much delayed).

Describe the solution you would like to see

• pyaeroval can be run for different models/variables in parallel, but to the same data directory
• the different model-runs don't interfere with each others.