Implement unified logger with log level -- part 1

[keremgocen]

Introduce a logging service to enhance error handling and debugging capabilities across various components of the application. Update configuration to include log level and format, and ensure that logging is integrated into the server and tool dependencies.

WIP: only integrated for the get-schema tool for now. Tests to follow.

Part 1: (in this PR)

• covers the foundations, a logger service with log levels from the MCP spec
• An MCP server hook allows MCP clients to set the level
• log format and output are decided at the start via env variables (although VSCode MCP client sets it to INFO and I could not find a way to change it)
• logger only implemented for the get-schema tool for now implemented for all tools
• added basic test coverage

Part 2: (not in this PR but here #95)

• Add a redaction mechanism to remove sensitive data
• Add test coverage

[MacondoExpress]

Really good! Left some comments, nothing of these are massive blocker IMO

[MacondoExpress]

From the reader perspective is not clear the intention of why we need the replaceAttr func rather than relying on the slog formatter.
From what I guess, it's because slog convert levels to string using a small subset of values:

• DEBUG
• INFO
• WARN
• ERROR

Giving back less granularity than what we desire, but as it's not tested the underline reason could be lost over time!

[keremgocen]

I added a doc string to explain what replaceAttr is used for. We also have a test already all log levels can be set dynamically and now we are checking for valid values so hopefully it should be a lot more clear.