feat: send some basic telemetry data

- Record # of CPU cores, memory, fragment database size, which features
  are turned on
- No identifications, quantitification, or identifiable data is tracked
- See CHANGELOG for more details

.github/workflows/rust.yml

@@ -29,5 +29,6 @@ jobs:
           -o foo \
           --annotate-matches \
           --write-pin \
+          --disable-telemetry-i-dont-want-to-improve-sage \
           tests/config-cli.json \
           tests/*.mzML

CHANGELOG.md

@@ -7,6 +7,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ## [Unreleased]
 ### Added
 - Support for semi-enzymatic digests (`database.enzyme.semi_enzymatic` parameter)
+- Ability to directly export matched fragment ions (e.g. for spectral library or rescoring) with the `--annotate-matches` CLI option. This is compatible with the `--parquet` CLI option as well. Annotations will be written to `matched_fragments.sage.tsv` or `matched_fragments.sage.parquet`
+- Sage sends basic telemetry data (version of Sage, run time, OS, # of CPU cores, # of peptides in database, whether LFQ is used) to a remote server. No information about your actual data is sent - e.g. identifications, quantities, organism, or modifications are NOT tracked or reported.  This data will be used to help focus efforts on improving Sage and figuring which features are most used. Please take a look at `crates/sage-cli/src/telemetry.rs` to see exactly what is sent! You can disable sending telemetry data  by using the `--disable-telemetry-i-dont-want-to-improve-sage` CLI flag.
+### Changed
+- Modified visibility on some crate internals to support the [sagepy project](https://github.com/theGreatHerrLebert/sagepy)
+- Added `psm_id` field to various output files to match the new `--annotate-matches` option.
+### Removed
+- Removed the `ms1_intensity` field from CSV output, since it is essentially useless
+
 
 ## [v0.14.4]
 ### Added