ci: set up CI/CD workflows

[anuragxxd]

Please describe your issue.

As part of improving our development workflow and ensuring a streamlined process for Continuous Integration (CI) and Continuous Deployment/Delivery (CD), we should consider implementing the necessary tools and practices in our project.

Additional context

Some of the tasks to follow are:

• ci: enforce semantic pull requests #33
• ci: static code analysis #42
• ci: automated testing #45
• feat(ci): calculate and report test coverage #245
• Building, Publishing, Versioning & Deployment #132
• feat: Documentation #142

Acknowledgement

We thank you for your valuable contribution and would like to acknowledge it
on our contributors page. To help us with that, we would like
to kindly request that you help us with this by commenting on this issue with
a request to the @all-contributors bot of the form
@all-contributors please add @YOUR_GH_HANDLE for TYPE_1, TYPE_2, ..., where
TYPE_1 etc. refer to contribution types supported by the All Contributors
Specification.

[uniqueg]

I think this is very high priority!

We don't necessarily need to address all of the listed aspects in a first draft, but having some automated testing/validation etc. is always better than none.

I would propose @git-anurag-hub or @SalihuDickson to take on a first GitHub Actions workflow ASAP.

[anuragxxd]

Cool! I will take it as parent of this is also assigned to me!

[uniqueg]

Let's leave this open and unassigned and have people assign the individual issues to themselves.

[JaeAeich]

@git-anurag-hub @uniqueg Hey how will Calculate and report test coverage be done, can I try it out? Maybe you can give me some resources on how to get this setup 😅 because I kinda don't know how this will even work out.

[uniqueg]

Basically, the idea is that in the CI we will use a test runner that will discover and run all tests for the repository, then compute the code coverage and report it (e.g., via CodeCov).

I don't know what a good test runner for JS/TS projects is, but perhaps this is one: https://about.codecov.io/blog/measuring-typescript-code-coverage-with-jest-and-github-actions/

@git-anurag-hub or @SalihuDickson may know better, I just extrapolated from the process we use for Python projects, where we use pytest as the test runner to run all tests in the tests/ directory (discovery is based on naming conventions).