amqp_client_SUITE: drop a non-essential flakey test

interference from other tests sometimes makes
it fail because there is more than one connection.

Compared to most other AMQP 1.0 tests, this one can be
dropped.

Author: michaelklishin

deps/rabbit/test/amqp_client_SUITE.erl

@@ -110,7 +110,6 @@ groups() ->
        idle_time_out_on_server,
        idle_time_out_on_client,
        idle_time_out_too_short,
-       rabbit_status_connection_count,
        handshake_timeout,
        credential_expires,
        attach_to_exclusive_queue,
@@ -4402,21 +4401,6 @@ idle_time_out_too_short(Config) ->
     after 5000 -> ct:fail({missing_event, ?LINE})
     end.
 
-rabbit_status_connection_count(Config) ->
-    %% Close any open AMQP 0.9.1 connections from previous test cases.
-    ok = rabbit_ct_client_helpers:close_channels_and_connection(Config, 0),
-
-    OpnConf = connection_config(Config),
-    {ok, Connection} = amqp10_client:open_connection(OpnConf),
-    receive {amqp10_event, {connection, Connection, opened}} -> ok
-    after 5000 -> ct:fail({missing_event, ?LINE})
-    end,
-
-    {ok, String} = rabbit_ct_broker_helpers:rabbitmqctl(Config, 0, ["status"]),
-    ?assertNotEqual(nomatch, string:find(String, "Connection count: 1")),
-
-    ok = amqp10_client:close_connection(Connection).
-
 handshake_timeout(Config) ->
     App = rabbit,
     Par = ?FUNCTION_NAME,