Use rules_erlang 3.5.0

and format MODULE.bazel with buildifier

Simplify check for non-amq exchanges

Bumps [actions/cache](https://github.com/actions/cache) from 3.0.6 to 3.0.7.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](https://github.com/actions/cache/compare/v3.0.6...v3.0.7

)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

By waiting for the first remove_replica command to complete we
may reduce the likelyhood of this test flaking.

amqp10_client system test suite reliability

Occasionally some system tests may fail as they start publishing
before the credit event has been received. Added a wait for condition
to avoid this.

Update prometheus to 4.9. close #4380

Some queue -> channel messages were missed from classic queues
when the queue type API was introduced. This commit fixes that
which should make use of classic queues portable outside of the
channel.

This includes some refactoring to make more explicit that
the stream_queue feature flag also enables queue types.

Revert "Set kernel param prevent_overlapping_partitions to true"

This reverts commit 8070344a.

We learnt during the last 6 days on master branch that RabbitMQ
- as of today - is not compatible with kernel parameter
`prevent_overlapping_partitions` set to `true`.

RabbitMQ explicitly disconnects node in at least two places:
1. rabbit_node_monitor to "promote" a partial network partition
to a full partition, and
2. rabbit_mnesia after a node reset to disconnect it from the
rest of the cluster.
There is no atomicity in the way we disconnect several nodes,
because it's a simple loop. Therefore, remote nodes may/will detect
disconnection at different times obviously. In global's new
behavior behind prevent_overlapping_partitions, our attempt to
disconnect all nodes in rabbit_mnesia creates a partial network
partition from global's point of view, leading to a complete
disconnection of the cluster.

For example, test
```
make ct-clustering_management t=cluster_size_3:join_and_part_cluster
```
was flaky and demonstrates the 2nd bullet point above where RabbitMQ
interfering with Erlang distribution conflicts with global's
prevent_overlapping_partitions.
When RabbitMQ resets a node, its last step is to loop over
clustered nodes and disconnect from them one at a time.
In this test with a 3-node cluster where we reset node A:
1. Node A instructs node B and C to remove node A from their view
   of the cluster
2. Node A disconnects from node B
3. global on node B get a nodedow event for node A, but node C is
   still connected to node A
4. global on node B concludes there is a network partition and
   disconnect from node A and node C
At this point, each node is on its own.
Nothing in RabbitMQ tries to restore the connection between
nodes B and C.

The correct path forward is:
1. Get rid of Mnesia replacing it with Khepri.
2. Once mirrored classic queues are removed, get rid of rabbit_node_monitor.
3. Have a clear and consistent view of the nodes comprising a RabbitMQ Cluster:
   In other words, do not use different sources of truths like nodes(),
   Mnesia, Ra clusters, global monitor at different places in the code.

For the time being we live with `prevent_overlapping_partitions` set to `false`
and with the workaround for global:sync/0 being stuck introduced in
https://github.com/rabbitmq/rabbitmq-server/commit/9fcb31f348590a74fd526333cf881cfbe27241e6

Streams: adapt tests to the latest Java stream client listener interface

Bump eetcd to 0.3.6

due to the changes in https://github.com/rabbitmq/ra/pull/298

'delivery' ra event is now received before 'applied' ra event.

See https://github.com/zhongwencool/eetcd/releases/tag/v0.3.6 for
details

Add StreamStats command to stream protocol

Other changes: returns a map of int64, use the new osiris:get_stats/1 API.

References #5412

Set kernel param prevent_overlapping_partitions to true

This kernel parameter got introduced in Erlang 24.3.
It is set to `false` by default in Erlang 24.
It is set to `true` by default in Erlang 25.

This commit requires Erlang >= 24.3.

As described in commit message
https://github.com/rabbitmq/rabbitmq-server/commit/4bf78d822d7496e03061119f4cb07c0b306e4c03
setting this flag to `true` will prevent global:sync/0 from hanging
in the presence of network failures.

Instead of relying on our own workaround of global:sync/0 being stuck
introduced in
https://github.com/rabbitmq/rabbitmq-server/commit/9fcb31f348590a74fd526333cf881cfbe27241e6
let us instead rely on the official Erlang fix that comes by setting
prevent_overloapping_partitions to true.

When a non-mirrored durable classic queue is hosted on a node
that goes down, prior to #4563 not only was the behaviour
that the queue gets deleted from the rabbit_queue table,
but also that its corresponding bindings get deleted.
The purpose of this test was to make sure that bindings
get also properly deleted from the new rabbit_index_route
table.

Given that the behaviour now changed #4563 we can either
delete this test or - as done in this commit - adapt this test.

How the behavior of this test should change
is yet to be discussed with @dcorbacho @ansd @lhoguin

HTTP API: allow connections to be listed and closed by username

Format code

Fix whitespace, fix warning

Update API docs

Remove blank lines

Add get all connections by username

Fix method name issue

Enable GET method to get connections by username

Update API documentation

Modify list all connections of username method

Remove list_by_username method and modify get all connections of user API

Code formatting, break up lines for readability

Refactor code to use pattern matching more effectively

Typo

Bumps [actions/cache](https://github.com/actions/cache) from 3.0.5 to 3.0.6.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](https://github.com/actions/cache/compare/v3.0.5...v3.0.6

)

---
updated-dependencies:
- dependency-name: actions/cache
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>

Pair: @the-mikedavis

Require Erlang 24.3

we expect that 3.11 GA will require 25.0 but this would do
for now

Drop Erlang 23 from Actions test matrix (in 3.12.x/master, 3.11.x)

we still use it for the 3.8.x mixed version umbrella,
for now