Add proper logging/monitoring

[MariusDieckmann]

Add better logging and monitoring for better overview of submitted and running jobs

[lukasjelonek]

According to the current functionality a good start would be to add the following log messages:

• New job '{Jobid}' received (=> .../startJob successfully send)
• Job '{Jobid}' started' (=> bakta-job starts), best with input data sizes to be able to monitor data throughput, e.g. Job 'Job {Jobid}' fasta file size: {size in bytes}, Job {Jobid}' prodigal training file size: {size in bytes}. If we ever plan to evaluate parameter usage, it would be good to include them as well in the logs.
• Job '{Jobid}' successfully finished (=> computation done)
• Job '{Jobid}' failed (=> computation failed)

[lukasjelonek]

• Job '{Jobid}' configuration: {configuration} to reproduce job settings

[lukasjelonek]

It might be good too also add a configuration option to enable debug logging for all components. This might be implemented by setting a DEBUG env variable and use it to trigger debug logs in production.