feat(jans-config-api): all config oprations should be logged to audit log or DB

Implement comprehensive logging capabilities to audit system activity and troubleshoot issues.

Acceptance Criteria:

- When Lock Config API operates then it shall generate lock_server_config.log for configuration events
- When logs are written then they shall include timestamp, event type, and relevant context data

Start at the Lock Config API entry point and inspect how configuration operations currently execute and where audit logs or the audit database are handled. Implement coverage for the stated configuration events, including timestamp, event type, and relevant context data, and verify that lock operations produce lock_server_config.log.

Written by the indexing model from the issue text.