Alignment and implementation of comprehensive Logging Concept

Nobody has claimed this yet.

**As** team
**I want** a comprehensive and consistent logging strategy (reflecting the current application)
**so that** this will improve my dev work in the best case

## Hints / Details
Log message:

- Incoming requests (Be aware of sensitive information - obfuscate sensitive information)
- Outgoing requests including all parameters (Be aware of sensitive information - obfuscate sensitive information)
- Stopwatch (Duration of request / response)
- Comprehensive logging in context of the EDC
- Using {} and varargs log.info("Error during starting of server: with name {} - response with status {}." , name, status )
- Think about adequate log level
- Using metrics where possible (time metrics, )
- Unique log messages for each log
- Meaningful log messages. Perspective, an external contributor which has to debug the code.

## Acceptance Criteria
- [ ] Alignment of common and comprehensive logging concept
- [ ] Short alignment in the team
- [ ] Alignment is written down in the Code Standards for BE
- [ ] Adapt changes to dev guideline (Github WIKI + Contribution.md)
- [ ] Check what is necessary to adapt in our product
- [ ] Optimize the logging in the application

## Out of Scope
- ...

Start by reading the Code Standards for BE, Github WIKI, and Contribution.md, then inspect the application's existing logging and metrics usage. Define the agreed logging concept, document it in those guidance locations, and identify and apply the necessary product changes while protecting sensitive information and using appropriate levels and messages.

Written by the indexing model from the issue text.