feat: action_status on action specific stream

[de-sh]

Closes #

Changes

Why?

We seek to send action responses onto two streams of the following form:

1. The original: /tenants/{tenant_id}/devices/{device_id}/action/status
2. The more action specific: /tenants/{tenant_id}/devices/{device_id}/action_status/{stream_name}

The action specific topics can hence forth be subscribed to receive notifications regarding progress of an action that is of interest.

Trials Performed

  2023-11-16T13:17:35.344081Z  INFO uplink::collector::simulator: Successfully sent all action responses

  2023-11-16T13:17:35.344317Z  INFO uplink::base::bridge::actions_lane: Action response = ActionResponse { action_id: "2223", action_name: None, sequence: 10, timestamp: 1700140655344, state: "Completed", progress: 100, errors: [], done_response: None }

  2023-11-16T13:17:35.344555Z DEBUG uplink::base::serializer: publishing on /tenants/demo/devices/1002/action/status with size = 109

  2023-11-16T13:17:35.344604Z DEBUG uplink::base::serializer: publishing on /tenants/demo/devices/1002/action_status/lock with size = 109

[de-sh]

The following is to help with custom templating of stream topics

[de-sh]

This change is to provide similar behavior from both action_status and the other response streams as otherwise we will see them pushing updates once every 100 points(MAX_BUF_SIZE) or 60 seconds(DEFAULT_TIMEOUT)

[de-sh]

An ActionResponse with action_name == None will go to the action_status stream i.e. topic: /tenants/{tenant_id}/devices/{device_id}/action/status
Whereas those with action_name == Some(stream_name) will go onto their streams and have the topic: /tenants/{tenant_id}/devices/{device_id}/action_status/{stream_name}