fix(server): resolve atomic value panic during config swap

[parastejpal987-cmyk]

What does this PR do?

Fixes a concurrency panic that occurs when atomic.Value attempts to store a different concrete type than what was initially stored.

Why is it necessary?

During rapid configuration reloads, the underlying type of the HTTP handler being stored in server.go could sometimes vary between different http.Handler implementations. Go's sync/atomic.Value panics if you try to store a value of a different concrete type than the first one stored.

How does it work?

Introduced a handlerWrapper struct to encapsulate the handler. By storing the wrapper instead of the raw handler, atomic.Value always receives the exact same concrete type, safely avoiding the panic while swapping configurations.