Describe the bug

Follow-up to #4238 and #5881

Reproduction steps

1. Start an AMQP 1.0 (git@github.com:lukebakken/Amqp10SessionExample.git) and AMQP 0.9.1 connection to RabbitMQ
2. Run rabbitmqctl list_amqp10_connections
3. Everything appears to work, but the log file will show the following:

   2023-09-12 04:39:57.314641-07:00 [error] <0.940.0> crasher: 2023-09-12 04:39:57.314641-07:00 [error] <0.940.0> initial call: rabbit_reader:init/3 2023-09-12 04:39:57.314641-07:00 [error] <0.940.0> pid: <0.940.0> 2023-09-12 04:39:57.314641-07:00 [error] <0.940.0> registered_name: [] 2023-09-12 04:39:57.314641-07:00 [error] <0.940.0> exception exit: {unexpected_message,{info,[pid],<0.1030.0>}} 2023-09-12 04:39:57.314641-07:00 [error] <0.940.0> in function rabbit_reader:handle_other/2 (rabbit_reader.erl, line 640) 2023-09-12 04:39:57.314641-07:00 [error] <0.940.0> in call from rabbit_reader:mainloop/4 (rabbit_reader.erl, line 531) 2023-09-12 04:39:57.314641-07:00 [error] <0.940.0> in call from rabbit_reader:run/1 (rabbit_reader.erl, line 453) 2023-09-12 04:39:57.314641-07:00 [error] <0.940.0> in call from rabbit_reader:start_connection/5 (rabbit_reader.erl, line 352) 

Expected behavior

No crashes in the log file.

Additional context

https://vmware.slack.com/archives/C055BSG8E/p1694516973608289

@ansd -

Things "appear" to be fine. But the underlying issue is how 1.0 connections are queried. 1.0 readers and 0.9.1 readers hang in the same position in the supervisor tree and have the same ID reader, hence that PR lists all 0.9.1 connections and all 1.0 connections.