Add support for ably-cli in agents header

Note that describing the ably-cli as a wrapper is arguably not correct, it's an application or perhaps a tool, but adding support for a new type is probably a lot of work, and at this stage, has limited value given we simply want a way to track ably-cli usage. The reason it's not correct is in the context of the data plane, ably-cli is not providing an API to end users, and wrapping functionality in an SDK, it is just a tool or app consuming. When it's calling the control plane, then it's not really an SDK as it's just a tool calling the API directly, and it's not a wrapper as it's not wrapping anything. If I categorised ably-cli as an SDK, then we'd also have the problem that the underlying SDK would not be logged as I believe only one SDK value is supported in most reports.

This commit also adds instructions for future people who want to make changes to agents to make them aware that agents are duplicated in our analytics pipeline processing.

Author: mattheworiordan

protocol/README.md

@@ -93,6 +93,7 @@ The following table adds more contextual detail for some agent identifiers, wher
 | ---------- | -------- |
 | `ably-asset-tracking-android` | [ably-asset-tracking-android](https://github.com/ably/ably-asset-tracking-android) |
 | `ably-asset-tracking-swift` | [ably-asset-tracking-swift](https://github.com/ably/ably-asset-tracking-swift) |
+| `ably-cli` | [ably-cli command line CLI too](https://github.com/ably/cli) |
 | `ably-flutter` | [ably-flutter](https://github.com/ably/ably-flutter) |
 | `ably-ruby-rest` | [ably-ruby](https://github.com/ably/ably-ruby) |
 | `android` | [ably-java](https://github.com/ably/ably-java), [ably-dotnet](https://github.com/ably/ably-dotnet) |
@@ -144,6 +145,8 @@ Therefore it is safe to publish without consulting others because they have an e
 
 #### Step 2: Internal
 
+**Go router support**
+
 Once the generated Go code has been updated, update the `ably-common-go` module in the
 internal [go-services](https://github.com/ably/go-services) repository by running:
 
@@ -154,6 +157,10 @@ go get -u github.com/ably/ably-common-go
 Open a pull request with the resulting changes to `go.mod` and `go.sum`, and once merged deploy the router
 so that it's aware of the newly added agent identifiers.
 
+**Analytics pipeline support**
+
+The agents are replicated in the analytics pipeline that processes agent headers. See [udtf_parse_ably_agent.py](https://github.com/ably/infrastructure/blob/main/terraform/modules/analytics/snowflake/files/functions/udtf_parse_ably_agent.py). Notify the Data / Infrastructure team of the changes in `agents.json` so that support in the analytics data pipeine is added.
+
 ### `ablyLibMappings`
 
 The `ablyLibMappings` field in [agents.json](agents.json) provides continuity for SDKs that continue to send the

protocol/agents.json

@@ -364,6 +364,11 @@
       "identifier": "chat-swift",
       "versioned": true,
       "type": "wrapper"
+    },
+    {
+      "identifier": "ably-cli",
+      "versioned": true,
+      "type": "wrapper"
     }
   ],
   "ablyLibMappings": {