ci: Refactor scripts

[febo]

Problem

CI currently has limited checks and the publish.yml workflow is limited to a couple of crates.

Solution

Refactor the CI. This involved using a new set of supporting scripts, which can also be used from the command-line:

• audit: audit dependencies of the workspace
• build: build a crate with build-sbf (useful to detect issues with code under the target = solana configuration
• clippy: run clippy
• doc: linting of doc sections
• format: run cargo fmt
• hack: linting of feature powerset
• lint: execute clippy && doc && hack in sequence
• semver: semantic versioning validation
• test: run cargo test

CI make use of these scripts to run:

1. audit
2. For each crate of the repository, it executes:
   • format
   • clippy
   • doc
   • hack
   • build
   • test

The publish.yml workflow was updated to work with any crate of the reposiroty and incorporates semver-checks based on the version level. If the version level selected for publishing violates semantic versioning, the publishing fails. For example, if the code to be published under a patch version contains breaking changes, the semver-check will fail and the publish workflow will abort.

Note

The code in main is currently failing the doc linting - #64 fixes these issues.

[febo]

Just realised that the "filter" is not as precise as it should be. For example, when the main pinocchio crate changes, all crates that depend on it should also go through the CI checks – this is not happening with the current filter.

Update: The conditional filter was removed.

[joncinque]

Nothing show-stopping, mostly small questions -- looks great!

[joncinque]

Why is the version specified like that?

[febo]

This is probably me not using the workspace dependencies correctly. I was trying to avoid bumping dependencies on other packages unnecessarily. For example, if pinocchio-pubkey can work with multiple versions of pinocchio and pinocchio has been bumped to 0.7, I still want to specify that pinocchio-pubkey works with anything from >= 0.6.

But perhaps this is not the correct way to do that.

[joncinque]

Ah I see, let's just keep them all at the same version for now, I think it'll make things simpler in the long run.

[joncinque]

A couple more comments, then this can go in!

[joncinque]

Ah I see, let's just keep them all at the same version for now, I think it'll make things simpler in the long run.

[joncinque]

Looks great!