CI and release pipeline

[narendraReddy45]

Description & motivation

This PR introduces CI and an automated release pipeline for the repository. Pushing a version tag builds for Linux and macOS, runs the test suite, packages the results, and publishes to GitHub Releases and JFrog Artifactory, end to end.

JIRA: https://jira.purestorage.com/browse/PEFM-362

Approach

• CI (every pull request) and the release pipeline (every tag) share the exact same build and test steps
• Linux is the primary gate: it runs the full test suite and builds both the servers and the command-line tools. macOS builds the command-line tools as well, giving Mac users a ready binary, and its result factors into the overall pipeline outcome.
• Servers are packaged as tarballs, matching how they're installed today. Everything else ships as a plain binary. Both lists are explicit, making it easy to see and adjust exactly what's included.
• Destinations are configurable: a release can go to GitHub, JFrog, or both, based on what's specified.
• Publishing is safely repeatable: a completed release stays protected from being overwritten, and running a publish again simply completes whatever remains, with nothing duplicated.
• Every published file includes its version in the filename, along with checksums, so anyone downloading a binary or tarball can verify exactly what was built.
• Release notes are generated automatically and organized into sections such as features, fixes, and breaking changes.

Testing

Tested in my personal fork and resulting release created when a tag is created
https://github.com/narendraReddy45/Dominator/releases/tag/v1.0.1-test