cli: Support multiple inputs in 'cat' (#1331)This adds support to the `mcap cat` command for multiple input files.Multiple files can be directly supplied, like    mcap cat file1.mcap file2.mcapor, the list of files may be auto-populated by your shell, enabling youto type    mcap cat **/*.mcap

rust: fix removal of identical channel data (#1339)### Changelog- Fixed: fixed a bug where when writing messages using`mcap::Writer::write(&Message{...})`, introduced in#1297 . Writingmessages on separate channels with identical channel data would causechannel data for some channels not to be written to the MCAP, resultingin an invalid MCAP.### DocsNone.### DescriptionMCAP as specified allows a 1:N relationship between channel content andchannel IDs. This is intentional - there may be multiple sourcespublishing the exact same topic, and the output MCAP can and shouldcontain one channel per publisher, not per topic.#1297 introduced the use of a bimap to track the relationship betweenchannel / schema IDs and their content. however, I overlooked at thetime a key constraint of the bimap implementation, in that all values onthe left and right side are unique.This means it could not track multiple identical channels or schemaswith the same ID. This PR introduces an additional (u16, u16) map forchannels and schemas which tracks the mapping of all IDs to their"canonical" IDs in the bimap. This allows us to track the presence ofmultiple records with the same content but different IDs, while alsopreserving the quick lookups that the bimap was introduced for.<!-- Describe the problem, what has changed, and motivation behind thosechanges. Pretend you are advocating for this change and the reader isskeptical. --><!-- In addition to unit tests, describe any manual testing you did tovalidate this change. --><table><tr><th>Before</th><th>After</th></tr><tr><td><!--before content goes here--></td><td><!--after content goes here--></td></tr></table><!-- If necessary, link relevant Linear or Github issues. Use `Fixes:foxglove/repo#1234` to auto-close the Github issue or Fixes: FG-### forLinear isses. -->

rust: bump cargo version (#1329)### Changelog- Added: Added options to disable CRC calculations in the rust writer- Changed: reduce allocations while writing messages### Docs<!-- Link to a Docs PR, tracking ticket in Linear, OR write "None" if nodocumentation changes are needed. -->### Description<!-- Describe the problem, what has changed, and motivation behind thosechanges. Pretend you are advocating for this change and the reader isskeptical. --><!-- In addition to unit tests, describe any manual testing you did tovalidate this change. --><table><tr><th>Before</th><th>After</th></tr><tr><td><!--before content goes here--></td><td><!--after content goes here--></td></tr></table><!-- If necessary, link relevant Linear or Github issues. Use `Fixes:foxglove/repo#1234` to auto-close the Github issue or Fixes: FG-### forLinear isses. -->

rust: release version 0.14.1 (#1324)### Changelog<!-- Write a one-sentence summary of the user-impacting change (API,UI/UX, performance, etc) that could appear in a changelog. Write "None"if there is no user-facing change -->None### Docs<!-- Link to a Docs PR, tracking ticket in Linear, OR write "None" if nodocumentation changes are needed. -->None### DescriptionBump the Rust version to 0.14.1 to release the `into_inner` changes.

Bump Python mcap-protobuf-support to v0.5.3 (#1323)Releasing#1321

@mcap/support: release 1.0.3 (#1319)Releasing#1318

go: fix lz4 invalid block checksum (#1309)### Changelog<!-- Write a one-sentence summary of the user-impacting change (API,UI/UX, performance, etc) that could appear in a changelog. Write "None"if there is no user-facing change -->cli: fixes error when input mcap file uses lz4 block checksums### Docs<!-- Link to a Docs PR, tracking ticket in Linear, OR write "None" if nodocumentation changes are needed. -->None### DescriptionAs noted in#1294 MCAP files created in Rust were failing when runthrough the MCAP CLI because of an invalid block checksum check in thelz4 decoder. This was fixed upstream so this change just updates thedependency.I've tested using `mcap doctor` and `mcap cat` on a file with thecorrect checksum and it passes with this change and fails without.<!-- Describe the problem, what has changed, and motivation behind thosechanges. Pretend you are advocating for this change and the reader isskeptical. --><!-- In addition to unit tests, describe any manual testing you did tovalidate this change. --><table><tr><th>Before</th><th>After</th></tr><tr><td><!--before content goes here--></td><td><!--after content goes here--></td></tr></table><!-- If necessary, link relevant Linear or Github issues. Use `Fixes:foxglove/repo#1234` to auto-close the Github issue or Fixes: FG-### forLinear isses. -->

Add into_inner() on Rust writer (#1314)### ChangelogAdd an `into_inner()` method on the Rust writer to get back theunderlying stream.### Docshttps://linear.app/foxglove/issue/FG-9969/[rust-sdk]-cant-close-mcap-writer### DescriptionSome I/O errors only show up when the output file is closed. This changeallows users to check for such errors.<!-- Describe the problem, what has changed, and motivation behind thosechanges. Pretend you are advocating for this change and the reader isskeptical. --><!-- If necessary, link relevant Linear or Github issues. Use `Fixes:foxglove/repo#1234` to auto-close the Github issue or Fixes: FG-### forLinear isses. -->Fixes:FG-9969

go: fix lz4 invalid block checksum (#1309)### Changelog<!-- Write a one-sentence summary of the user-impacting change (API,UI/UX, performance, etc) that could appear in a changelog. Write "None"if there is no user-facing change -->cli: fixes error when input mcap file uses lz4 block checksums### Docs<!-- Link to a Docs PR, tracking ticket in Linear, OR write "None" if nodocumentation changes are needed. -->None### DescriptionAs noted in#1294 MCAP files created in Rust were failing when runthrough the MCAP CLI because of an invalid block checksum check in thelz4 decoder. This was fixed upstream so this change just updates thedependency.I've tested using `mcap doctor` and `mcap cat` on a file with thecorrect checksum and it passes with this change and fails without.<!-- Describe the problem, what has changed, and motivation behind thosechanges. Pretend you are advocating for this change and the reader isskeptical. --><!-- In addition to unit tests, describe any manual testing you did tovalidate this change. --><table><tr><th>Before</th><th>After</th></tr><tr><td><!--before content goes here--></td><td><!--after content goes here--></td></tr></table><!-- If necessary, link relevant Linear or Github issues. Use `Fixes:foxglove/repo#1234` to auto-close the Github issue or Fixes: FG-### forLinear isses. -->

fix pypi publishing (#1312)### ChangelogNone### DocsNone### DescriptionSee alsofoxglove/foxglove-sdk#158.> Running a publish to TestPyPI immediately followed by a publish to the"real" PyPI triggered an error due to a file already existing. Theworkaround recommended inpypa/gh-action-pypi-publish#283 (comment)is to set `attestations: false` on the TestPyPI publish.