Say that telemetry off does not stop mapbox report

A report is something someone ran on purpose, so it still fetches the CLI's token from cli.mapbox.com with telemetry off. The README's opt-out section and the report docs now say so, and an end-to-end test holds it for `config set telemetry off`.

Author: zmofei

README.md

@@ -702,6 +702,11 @@ or, to turn it off in every shell,
 mapbox config set telemetry off
 ```
 
+Opting out does not stop [`mapbox report`](#feedback-about-the-cli), since
+you run it on purpose: it still fetches the CLI's token from
+`https://cli.mapbox.com/config/token.json` when it has none, and sends your
+message with the CLI's version and OS appended.
+
 For additional information on our data processing activities and your
 related rights, please see our Mapbox
 [Privacy Policy](https://www.mapbox.com/legal/privacy).

docs/commands.md

@@ -2034,7 +2034,10 @@ revoked with no new one yet, this API refuses it, or it is rate-limited
 your token, though the message is still filed under Mapbox's account. With
 none of your own, the command fails with `cli_token_unavailable` or
 `cli_token_forbidden`, or with the `429` itself. Each run tries the CLI's
-token again; nothing here is put off for later.
+token again; nothing here is put off for later. Turning telemetry off does
+not change any of this: a report is something you ran on purpose, so it
+still fetches the CLI's token from `https://cli.mapbox.com/config/token.json`
+when it has none.
 
 #### Parameters
 

tests/dry_run.rs

@@ -813,6 +813,23 @@ mod report_token {
         assert!(state.contains(r#""token":"pk.fresh""#), "{state}");
     }
 
+    /// Telemetry off stops the background fetch, not `report`: someone ran
+    /// it on purpose. Every run here sets `MAPBOX_CLI_NO_TELEMETRY`; this
+    /// adds the setting.
+    #[test]
+    fn telemetry_off_does_not_stop_report_fetching() {
+        let config = config_dir("report-telemetry-off");
+        let set = run(&config, &["config", "set", "telemetry", "off"]);
+        assert!(set.status.success(), "{}", stderr(&set));
+        let out = sent_nowhere(&config, &["--debug", "report", "A test"])
+            .env("MAPBOX_INTERNAL_CLI_TOKEN_URL", token_endpoint("pk.fresh"))
+            .output()
+            .expect("run mapbox");
+        let state = std::fs::read_to_string(config.join("cli-token.json"))
+            .unwrap_or_else(|_| panic!("nothing fetched: {}", stderr(&out)));
+        assert!(state.contains(r#""token":"pk.fresh""#), "{state}");
+    }
+
     /// A command fetches past the backoff, so the reason it gives is what
     /// that fetch found, not the backoff's wait, which it never waited for.
     #[test]