Closes #604.

This moves the mulitcast feature under applications, to enforce that all
devices within the multicast group belong to the same application as the
multicast group.

Before you upgrade, please validate that if you have any existing
multicast-groups that:

1. These are not empty (they contain one or multiple devices)
2. All devices within the multicast group belong to the same
application

If these conditions are met, ChirpStack Application Server will
automatically migrate your multicast group(s) to the same application as
your devices. In any other case, the migration will throw an
error asking you to either remove the empty multicast group(s) or to
re-assign the devices so that the above criteria are met.

Closes #590 #409.

By using a Redis Stream instead of Pub/Sub, the last N frames can be
retained, making debugging easier.

This also updates the Redis client to v8, so that it is possible to
cancel the blocking XRead operation (v7 did not support this).

Signed-off-by: SAGAR PATEL <sagar.a.patel@slscorp.com>
Co-authored-by: Orne Brocaar <info@brocaar.com>

This method is used by the ChirpStack Network Server when it needs to
update the frame-counter sequence of the queue-items, e.g. when the
downlink frame-counter was incremented by a mac-command only downlink.

Note: changing the frame-counter of a downlink requires re-encryption as
the frame-counter is one of the encryption parameters.

Signed-off-by: SAGAR PATEL <sagar.a.patel@slscorp.com>
Co-authored-by: Orne Brocaar <info@brocaar.com>

Signed-off-by: SAGAR PATEL <sagar.a.patel@slscorp.com>
Co-authored-by: Orne Brocaar <info@brocaar.com>

The updated version contains the request cancellation fix.

When the global MQTT integration is enabled, this makes it possible for
users to generate a TLS client-certificate for authentication /
authorization with the MQTT broker.

When using for example Auth0, this makes it possible to configure the
Auth0 logout endpoint (potentially redirecting back to a login page).

This way, the user is not only logged out from the web-interface, but
also from the identity provider.

Closes #519.

This can be used for testing the HomeNSReq when ChirpStack Application
Server is used as a join-server, it is not intended for production use.

A Home NetID can be set per device by setting a 'home_netid' variable in
the device configuration.

As the integrtion in its new form does not maintain a connection, it
will be possible to provide this integration as an application
integration which can be configured through the web-interface.

This makes the integration easier to maintain as it does not keep a
connection state with the Azure Service Bus endpoint. As the Azure
Service Bus does not deal with re-connect logic, this had to be
implemented within the integration.

Since the integration does no longer keep a connection state, it can be
made available through the web-interface as there is no downside when
many instances of this integration exist for different applications.

Closes #427.

Instead of configuring a separate URL per event-type, this posts all
events to a single endpoint with an `eventType` url query argument
indicating the event-type.

This reduces the amount of configuration and does not require to create
new endpoints when new events are added.

This is fully backwards compatible as already configured endpoints for
specific events will override the new event endpoint url.