Establish CI with GitHub Actions, Automatic Tagging, and Makefile

[piraz]

This issue proposes to set up a strong continuous integration (CI) foundation for the project, including:

• Create a GitHub Actions workflow for the CI pipeline (build, test, lint, etc.)
• Implement automatic version tagging upon successful releases (using GitHub Actions and/or Makefile targets)
• Provide a clean, useful Makefile to streamline local development and CI steps (e.g., test, lint, release, etc.)

Goals:

• Ensure all changes are validated by CI before merging
• Make release/tags fully automated when merging to main branch
• Lower the barrier for contributors by documenting Makefile targets and CI structure

Acceptance Criteria:

• Project contains a .github/workflows/ci.yml or similarly named workflow
• Makefile available in the root folder with at least test, lint, build, and release/tag targets
• GitHub Actions handle auto-tagging when criteria are met (release branch/main, passing CI)
• Documentation in README about CI, Makefile, and release steps