GitHub automated build and releases

[trailcode]

Description

The project has no automated builds or published releases. Users are directed to "Download the latest release" in usage.md, but there is no GitHub Actions workflow to build the project or create release artifacts. Setting up CI/CD would allow:

• Automated builds (e.g. Windows, and optionally WebAssembly) on push or tag
• Release artifacts (installers or binaries) attached to GitHub Releases
• Users to download pre-built binaries instead of building from source (see README.md)

Expected behavior

• GitHub Actions workflow(s) build EzyCad (native and/or WebAssembly) when triggered (e.g. on tag, or on push to main).
• Successful builds produce artifacts that can be published to Releases.
• usage.md Installation step 1 can link to the latest release instead of only to README build instructions.

Actual behavior

• No .github/workflows or other CI configuration exists.
• Releases page is empty; users must build from source using README.

Scope (suggested)

• Add a workflow that builds the project (e.g. Windows with VS, OCCT, and dependencies).
• Optionally add a workflow or job for Emscripten/WebAssembly build.
• On release tag (e.g. v*), build and upload artifacts and create/update a GitHub Release.
• Document in README how to obtain release builds once available.

Environment

• Repository: GitHub (trailcode/EzyCad)
• Build: CMake, OCCT, NuGet, etc. as in README.md

References

• usage.md → Getting Started → Installation: "Download the latest release" points to README and notes that automated builds are not yet available.
• README.md: Building Instructions.