Describe the bug

INFO all returns an empty response, while INFO (without arguments) and INFO <section> (e.g., INFO server) work correctly.

This breaks compatibility with monitoring tools like [Netdata](https://github.com/netdata/netdata), which use INFO all to collect metrics from Redis-compatible servers. As a result, Garnet cannot be monitored by these tools out of the box.

Steps to reproduce the bug

# Works — returns all sections
redis-cli -p 6380 INFO
# (returns full output: server, memory, stats, etc.)

# Works — returns specific section
redis-cli -p 6380 INFO server
# # Server
# garnet_version:1.1.1
# os:Unix 6.8.0.106
# ...

# Bug — returns empty
redis-cli -p 6380 INFO all
# (empty response)

Expected behavior

INFO all should return the same output as INFO (without arguments), as per the [Redis documentation](https://redis.io/docs/latest/commands/info/):

When no argument is provided, the default set of sections is returned. When the all argument is passed, all sections are included.

Screenshots

No response

Release version

v1.1.1

IDE

No response

OS version

Ubuntu 24.04

Additional context

• Installation method: dotnet tool install garnet-server
• Redis client: redis-cli (redis-tools)

Impact

Monitoring tools that implement the Redis protocol (Netdata, Prometheus redis_exporter, Datadog, etc.) typically use INFO all to collect metrics. The empty response causes these collectors to fail, meaning Garnet cannot be monitored as a drop-in Redis replacement without workarounds.