ci: find way to catch build issues related to cargo publish at PR creation time

[WesleyRosenblum]

Problem:

#2009 added additional checks to the CI that ensure that the cargo package command succeeds on every PR. This was intended to catch build issues that a normal cargo build does not catch prior to publishing the crates. cargo package works by pulling dependencies (including those in the workspace) directly from crates.io, meaning that when changes are made in one crate that depend on another crate, the cargo package command may fail.

Solution:

TBD. If there were a way to run cargo package using local workspace versions, that could potentially work.

Requirements / Acceptance Criteria:

A pull request that contains changes that will prevent cargo publish from succeeding will fail CI; otherwise the CI must pass