ci: reduce redundant workflow work

[membphis]

Summary

• add a shared Linux release cdylib artifact and reuse it from Lua/OpenResty/valgrind jobs
• reduce OpenResty full busted coverage to the latest runtime while keeping smoke + resty -V on all OpenResty images
• keep ci: 缩短 CI 关键路径执行时长（实测 12.5min → ~9min） #110's standalone blocking LuaJIT valgrind job, but remove its duplicate Rust build by consuming the shared artifact
• move PR fuzzing to deterministic corpus replay and add scheduled timed fuzzing
• make cargo-audit use a prebuilt installer, run on dependency changes, and add a weekly audit workflow
• extract reusable Lua setup, Lua dependency install, LuaJIT resolution, and latest-rockspec selection helpers
• add PR concurrency and fold macOS LuaRocks validation into the macOS Rust job

Notes

• I checked branch protection through the GitHub API and main currently reports Branch not protected, so there are no required status checks to update from this PR.
• Rebased on origin/main after ci: 缩短 CI 关键路径执行时长（实测 12.5min → ~9min） #110 landed; the new blocking valgrind job is preserved.

Verification

• cargo test --release
• cargo test --release --no-default-features
• make lint
• isolated LuaJIT 5.1 tree: make test LUAJIT=/opt/homebrew/bin/luajit
• isolated LuaJIT 5.1 tree: make lua-lint
• /tmp/lua-qjson-tools/actionlint
• git diff --check
• python3 -m py_compile .github/scripts/latest-rockspec.py
• bash -n .github/scripts/resolve-luajit.sh .github/scripts/run-openresty-runtime.sh .github/scripts/install-lua-test-deps.sh
• cargo +nightly fuzz run fuzz_parse_eager -- -runs=0
• cargo +nightly fuzz run fuzz_parse_lazy -- -runs=0
• cargo +nightly fuzz run fuzz_depth -- -runs=0
• cargo +nightly fuzz run fuzz_ffi_ops -- -runs=0
• GitHub CI run 26705820767 passed, including standalone blocking Lua valgrind memcheck (upstream LuaJIT)

Closes #111

[coderabbitai]

Warning

Review limit reached

@membphis, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 37 minutes and 12 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b44b06bc-1cdc-4245-a726-47513e45d69a

📥 Commits

Reviewing files that changed from the base of the PR and between 37d60b2 and b99d098.

📒 Files selected for processing (11)

• .github/actions/setup-lua/action.yml
• .github/scripts/install-lua-test-deps.sh
• .github/scripts/latest-rockspec.py
• .github/scripts/resolve-luajit.sh
• .github/scripts/run-openresty-runtime.sh
• .github/workflows/changelog-policy.yml
• .github/workflows/ci.yml
• .github/workflows/fuzz.yml
• .github/workflows/lua-lazy-mutation-property.yml
• .github/workflows/release.yml
• .github/workflows/supply-chain-audit.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/111-ci-dedupe

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}