fix: Prevent memory leaks caused by pull query logging

[AlanConfluent]

Description

This changes Pull Queries to use a fixed logger name rather than use the query id. KSQL otherwise gets OOM Errors after doing high QPS for half an hour, due to creating so many unique loggers.

This is because both in the class io.confluent.common.logging.StructuredLoggerFactory and in the slf4j Logger factory itself, they keep a ConcurrentMap of name -> Logger to reuse loggers. After many, many queries, you eventually get OOMs if you create a new one every pull query.

Fixes #5527

Testing done

Profiled memory before and after change.

Reviewer checklist

• Ensure docs are updated if necessary. (eg. if a user visible feature is being added or changed).
• Ensure relevant issues are linked (description should include text like "Fixes #")

[agavra]

LGTM! Nice sleuthing

[rodesai]

LGTM