Use Input/Output IDs instead of passing pointers through C

[CraftSpider]

This both reduces the chance of weird soundness issues in relation to pointer provenance, and prepares the way for #1138

[codecov]

Codecov Report

Attention: Patch coverage is 63.31658% with 73 lines in your changes missing coverage. Please review.

Project coverage is 47.06%. Comparing base (825e11b) to head (f8318ad).
Report is 8 commits behind head on master.

Files with missing lines	Patch %	Lines
crates/bridge_core/src/lib.rs	85.18%	12 Missing ⚠️
crates/pdf_io/pdf_io/dpx-dpxfile.c	0.00%	12 Missing ⚠️
crates/pdf_io/pdf_io/dpx-tt_cmap.c	0.00%	9 Missing ⚠️
crates/pdf_io/pdf_io/dpx-dvi.c	33.33%	4 Missing ⚠️
crates/pdf_io/pdf_io/dpx-truetype.c	0.00%	4 Missing ⚠️
crates/engine_xetex/xetex/xetex-synctex.c	78.57%	3 Missing ⚠️
crates/pdf_io/pdf_io/dpx-cidtype2.c	0.00%	3 Missing ⚠️
crates/pdf_io/pdf_io/dpx-subfont.c	0.00%	3 Missing ⚠️
crates/pdf_io/pdf_io/dpx-vf.c	0.00%	3 Missing ⚠️
crates/pdf_io/pdf_io/dpx-cidtype0.c	0.00%	2 Missing ⚠️
... and 13 more

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1286      +/-   ##
==========================================
- Coverage   47.06%   47.06%   -0.01%     
==========================================
  Files         184      184              
  Lines       66302    66300       -2     
  Branches    66302    66300       -2     
==========================================
- Hits        31206    31202       -4     
- Misses      35096    35098       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[CraftSpider]

@Mrmaxmeier sorry to ping you again, tectonic-on-arXiv isn't appearing. If it would be helpful, is there anything I can do myself to triage/fix this kind of thing?

[Mrmaxmeier]

@Mrmaxmeier sorry to ping you again, tectonic-on-arXiv isn't appearing. If it would be helpful, is there anything I can do myself to triage/fix this kind of thing?

No problem 🙂 Results should come in in a bit.
The machine that this was running on was retired a bit ago, so I've moved it somewhere else now. Looks like I'll need to bump up the test timeouts though since the new server is much slower. In the mean time it'll show a few "crashed" builds.