Unsuback user callback is invoked with no context

[bretambrose]

The unsuback handler calls the user callback with null:

MQTT.js/lib/client.js

Lines 1657 to 1662 in accd78e

	case 'unsuback': {
	delete this.outgoing[messageId]
	this.messageIdProvider.deallocate(messageId)
	this._invokeStoreProcessingQueue()
	cb(null)
	break

There doesn't seem to be a way to get any of the reason codes from the unsuback (let alone reason string and user properties).

Adding the packet to the callback invocation might not be a breaking change, but it might also be a surprise if the recipient was used to a null value for the packet.

[github-actions]

This is an automated message to let you know that this issue has
gone 365 days without any activity. In order to ensure that we work
on issues that still matter, this issue will be closed in 14 days.

If this issue is still important, you can simply comment with a
"bump" to keep it open.

Thank you for your contribution.

[robertsLando]

@bretambrose would you like to submit a PR?

[github-actions]

This is an automated message to let you know that this issue has
gone 365 days without any activity. In order to ensure that we work
on issues that still matter, this issue will be closed in 14 days.

If this issue is still important, you can simply comment with a
"bump" to keep it open.

Thank you for your contribution.