ci: Move cargo doc test back to test pipeline

[def-]

and use the dedicated agents. Depends on https://github.com/MaterializeInc/i2/pull/2841

For https://materializeinc.slack.com/archives/C01LKF361MZ/p1758285899379379

Fixes: https://github.com/MaterializeInc/database-issues/issues/9717

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

[antiguru]

Thank you!