Implementation, testing and req tracing for reset() operation

[AnotherDaniel]

The Reset() operation defined by the usubscription spec was missing entirely so far, this change implements that, plus any adjacent required changes and functionality.

Implements:

• dsn~usubscription-reset-protobuf~1
• req~usubscription-reset~1
• req~usubscription-reset-only-usubscription~1

[sophokles73]

I am not sure if I understand the use case. Is the up-subscription-cli supposed to be used for interacting with a uSubscription service running as a separate process? If so, then using LocalTransport will not work because it can only be used for communication within the same process, i.e. it does not support remote invocation of services across process boundaries ...

[AnotherDaniel]

No, the cli is simply a configuration frontend for running up-subscription service. It sets up up-transports according to configuration, then hands them over to up-susbcription to use.

Also at the moment, the local transport is the only thing that can be made to compile, until mqtt5 and zenoh up-transports are made available to use the latest up-rust revision (that includes the reset() changes that were done to accommodate this PR here).

[sophokles73]

LGTM