Split CI to build and test jobs (#8359)

The CI has been re-organized with the following:
```
ci.yml (Main Orchestrator)
├── filter job
│   ├── Documentation Only? → Yes → Skip CI
│   └── Documentation Only? → No → Continue CI
│
├── Build Jobs
│   └── ci-slang-build.yml
│       ├── common-setup action
│       ├── Build & Package
│       └── Upload Artifacts (Build package and Tests package)
│
└── Test Jobs
    └── ci-slang-test.yml
        └── common-test-setup action
            ├── Download Tests Artifacts ← (from Build)
            └── Run Tests
```

To achieve fine-grained build->test dependency, instead of using `matrix
strategy` in single build (or single test) job, the main ci.yml
statically defines the each config of the build and test job.
e.g. `build-windows-debug-cl-x86_64-gpu` and
`test-windows-debug-cl-x86_64-gpu` are a pair of the build-test job for
the windows/debug/ci config.


Closes: https://github.com/shader-slang/slang/issues/6728

---------

Co-authored-by: slangbot <ellieh+slangbot@nvidia.com>
Co-authored-by: slangbot <186143334+slangbot@users.noreply.github.com>

0 files changed, 0 insertions, 0 deletions