fix(ci): repair the publish chain so the workflow can actually run

[beyondnetPeru]

Same defect and same fix as beyondnetcode/Shell.Aop#8, which is already merged and green. build.yml is copy-pasted across the Shell.* family, so every repo inherited it.

Root cause

on: declared tags: as a top-level key, which is not a GitHub Actions event:

on:
  push:
    branches: [main, develop]
  pull_request:
    branches: [main, develop]
  tags:          # <- not a valid event
    - 'v*'

GitHub rejects the whole file. Every run in this repo's history failed in 0 seconds with "This run likely failed because of a workflow file issue" — CI has never executed, and the 5 tests in this repo have never run on any commit.

Fixes

• tags: ['v*'] moved under push:
• version job: dropped github.event_name == 'tag' — tag pushes arrive as push
• pack matrix points at the real project locations (repo root, not src/)
• -p:PackageVersion= replaces --version:, which is not a dotnet pack option
• --no-build dropped; the job runs on a fresh runner with nothing pre-built
• matrix values are folder names — upload-artifact rejects names containing /
• release now depends on publish, so no Release appears for packages that never shipped
• workflow renamed CI / CD → CI; README badge switched to the file-based URL

Verification

Locally on .NET 10.0.201 (matching global.json):

dotnet build BeyondNet.Bootstrapper.sln -c Release  → 0 errors (2 warnings)
dotnet test  BeyondNet.Bootstrapper.sln -c Release  → 5/5 passed
dotnet pack  <each of the 4 matrix projects> -p:PackageVersion=9.9.9-test

All four packages produced with the version in the filename and a populated lib/net10.0/.

Before releasing

NUGET_API_KEY must exist in the nuget-release environment, or publish fails at the last step.

🤖 Generated with Claude Code