ci: overhaul

[crazyscot]

ISSUE 17 - Overhaul CI

Fixes #17. Coveralls report

Description

This branch necessarily incorporates PR #18.

• Replace deprecated actions with more modern ones
• Add rust-cache to the build step
• Rebuild coverage workflow using taiki-e/cargo-llvm-cov
• Run the various build steps with --locked
  • This could be controversial. This is what I do in my own repos, but I'm happy to back that out if preferred.
• Include clippy fixes from style: fix clippy warnings #18

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist

• My code follows the contribution guidelines of this project
• I have performed a self-review of my own code
• [N/A] I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I formatted the code with cargo fmt
• I checked my code using cargo clippy and reports no warnings
• I have added tests that prove my fix is effective or that my feature works
• [N/A] The changes I've made are Windows, MacOS, Linux compatible (or I've handled them using cfg target_os)
• I increased or maintained the code coverage for the project, compared to the previous commit

Acceptance tests

wait for a project maintainer to fulfill this section...

• regression test: ...

[crazyscot]

Updated as requested: Cargo.lock untracked, all instances of --locked removed from the workflows.

[coveralls]

Pull Request Test Coverage Report for Build 12349180208

Details

• 42 of 42 (100.0%) changed or added relevant lines in 3 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+1.9%) to 99.407%

---

Files with Coverage Reduction	New Missed Lines	%
src/parser/mod.rs	1	99.64%

Totals
Change from base Build 8204148435:	1.9%
Covered Lines:	1676
Relevant Lines:	1686

---

💛 - Coveralls

[veeso]

Thank you so much for this pr!