Improve CI/CD pipelines with gitflow and conventions

[alexandrebpetit]

Summary

• Add develop branch to CI pull_request triggers
• Add CI push triggers on develop, release/*, hotfix/*
• Add logLevel options (minimal/normal/detailed/diagnostic, default: minimal)
• Dynamic verbosity in all dotnet test steps (${{ inputs.logLevel || 'minimal' }})
• Switch CD tag format from v* to semver without prefix (1.0.0)
• Add get-version job that extracts version from Git tag and injects it into .csproj before pack

Impact

The NuGet package version is now driven by the Git tag — no more risk of tag/package version mismatch.

[Copilot]

Pull request overview

Updates the GitHub Actions CI/CD workflows to better support a gitflow-style branching model and to drive NuGet package versions from Git tags to prevent tag/package version mismatches.

Changes:

• Expanded CI triggers to include PRs targeting develop and pushes to develop, release/*, and hotfix/*.
• Added configurable logLevel inputs and attempted to apply them to dotnet test verbosity.
• Changed CD tag trigger format to SemVer-like tags and added a get-version job to inject the tag version into the .csproj prior to packing.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 8 comments.

File	Description
.github/workflows/ci.yml	Adds gitflow branch triggers and introduces dispatch-controlled test verbosity.
.github/workflows/cd.yml	Switches to SemVer tag triggers, adds version extraction, and injects version into the packed NuGet artifact.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.