Add crate publish test to ci

[mircea-c]

Problem

Publishing crates to crates.io sometimes fails during releases leaving versions in an inconsistent state.

Summary of Changes

Add an extra task to the crate-check workflow which publishes the crates to a test repo.

Closes https://github.com/anza-xyz/devops/issues/299

[yihau]

if we won't plan to add cron jobs for it, I guess we can put this step into the same place

agave/ci/buildkite-pipeline.sh

Lines 183 to 188 in 4f4b819

	command_step checks1 "ci/docker-run-default-image.sh ci/test-checks.sh" 20 check
	command_step dcou-1-of-3 "ci/docker-run-default-image.sh ci/test-dev-context-only-utils.sh --partition 1/3" 20 check
	command_step dcou-2-of-3 "ci/docker-run-default-image.sh ci/test-dev-context-only-utils.sh --partition 2/3" 20 check
	command_step dcou-3-of-3 "ci/docker-run-default-image.sh ci/test-dev-context-only-utils.sh --partition 3/3" 20 check
	command_step miri "ci/docker-run-default-image.sh ci/test-miri.sh" 5 check
	command_step frozen-abi "ci/docker-run-default-image.sh ./test-abi.sh" 15 check

instead of triggering a different pipeline 🤔

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.8%. Comparing base (6b322ca) to head (d8db10b).
Report is 8 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##           master    #6332     +/-   ##
=========================================
- Coverage    82.8%    82.8%   -0.1%     
=========================================
  Files         847      847             
  Lines      379497   379497             
=========================================
- Hits       314307   314302      -5     
- Misses      65190    65195      +5     

🚀 New features to boost your workflow:

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

[mergify]

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.

[steviez]

#6440 and #6525 both landed so this one can be rebased when you get around to it

[mergify]

If this PR represents a change to the public RPC API:

1. Make sure it includes a complementary update to rpc-client/ (example)
2. Open a follow-up PR to update the JavaScript client @solana/kit (example)

Thank you for keeping the RPC clients in sync with the server API @mircea-c.

[mergify]

The Firedancer team maintains a line-for-line reimplementation of the
native programs, and until native programs are moved to BPF, those
implementations must exactly match their Agave counterparts.
If this PR represents a change to a native program implementation (not
tests), please include a reviewer from the Firedancer team. And please
keep refactors to a minimum.

[mircea-c]

FFS. I messed up a git rebase. Closing this and will push a new PR with the changes 😔

[t-nelson]

new one is here #6550

FWIW, in the future, you can just force push over your feature branch that the pr was created from and github will update the pr as if nothing happened