Github Actions and AWS PyPi Build

[H00N24]

In this PR we're a GitHub actions pipeline that builds the cvldoc_parser package and pushes it into our private CodeArtifacts PyPi.

To avoid issues with version rewriting we're using dynamic versioning using git following the PEP440 standard as {base}(.post{distance}.dev0+{commit})? (currently 0.0.0.post208.dev0+ca38360).

If we create a new GitHub tag v2.0.2 the release build would be 2.0.2 and all further commits until the next release would be versioned as 2.0.2.post12.dev0+c3an45.

Currently, we're supporting all major platforms with basic testing. On push to master or GH release we'll build all of them and upload them to both CodeArtifacts PyPi and the GH Release page.

@ozcodes do you think we should keep the CircleCI or should we move everything to GitHub Actions?

@pickx I had to remove some Rust code as I was getting errors during the cargo test, was it expected (57fe133)?

error: unused imports: `cvl_parser`, `decl_parser`
Error:  --> src/parse/tests/cvl2.rs:1:20
  |
1 | use crate::parse::{cvl_parser, decl_parser};
  |                    ^^^^^^^^^^  ^^^^^^^^^^^
  |
  = note: `-D unused-imports` implied by `-D warnings`
  = help: to override `-D warnings` add `#[allow(unused_imports)]`

error: trait `ToSpan` is never used
Error:   --> src/parse/builder.rs:86:7
   |
86 | trait ToSpan {
   |       ^^^^^^
   |
   = note: `-D dead-code` implied by `-D warnings`
   = help: to override `-D warnings` add `#[allow(dead_code)]`

error: could not compile `cvldoc_parser_core` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `cvldoc_parser_core` (lib test) due to 2 previous errors```

Here is an example of a successful run:

• https://github.com/Certora/cvldoc_parser/actions/runs/9005898838/job/24742499303

[ozcodes]

@H00N24 went though the ci part, overall very good, I'm all for working with github instead of circleci, I left comments about some minor things

[ozcodes]

are there other options besides success and failure ?

[pickx]

I was also puzzled by this - https://stackoverflow.com/a/58859404 explained it:

If you don't want the function to run when you manually cancel a job [...]

maybe the suggested '!cancelled()' alternative is more readable

[H00N24]

Yes, this is an old trick to do allow_failure: true as in Gitlab CI (run tests even if the syntax check failed). I was not using '!canceled()' as GH VS Code extension will try to reformat to "!canceled()" and then complaints that it should not start with "...

[pickx]

nice. lgtm.