ci: Split code coverage into Package Test and Project Test jobs

[unity-nikos]

Purpose of this PR

Splits the code coverage Yamato config into two focused jobs so coverage is measured for both the package's own tests and the in-repo testproject:

• Converts the existing Code Coverage - NGO [ubuntu, 6000.3] job into [Code Coverage] Package Test - NGO [ubuntu, trunk] (id code_coverage_package_test_ubuntu_trunk). Same coverage command as before; editor moved to trunk.
• Adds [Code Coverage] Project Test - NGO testproject [ubuntu, trunk] (id code_coverage_project_test_testproject_ubuntu_trunk) — a single instance that runs the testproject EditMode/PlayMode tests with coverage enabled (deps run_quick_checks + package-pack, matching project-tests.yml).

Trigger wiring in _triggers.yml — both coverage jobs run together on:

• PR changes (pr_code_changes_checks) — replaces the old code_coverage_ubuntu_{{ validation_editors.default }} reference.
• Nightly (develop_nightly).

(Neither job runs in the weekly trigger.)

Both jobs stay single-instance (Ubuntu, trunk) since coverage doesn't vary meaningfully across platforms/editors.

Jira ticket

TODO: link ticket (e.g. MTT-XXXX)

Changelog

Not applicable — CI-only change, no package/public-facing changes.

Documentation

• No documentation changes or additions were necessary.

Testing & QA (How your changes can be verified during release Playtest)

Rendered every .yamato/*.yml through a local Liquid renderer and verified:

• Both new jobs template to valid YAML with the expected ids/names.
• All trigger references to the coverage jobs resolve (PR + nightly, for both jobs).
• The Project Test job's run_quick_checks dependency exists in _run-all.yml.

Final verification is the Yamato jobs themselves running green on this PR.

Functional Testing

Manual testing :

• Manual testing done

Automated tests:

• Covered by existing automated tests
• Covered by new automated tests

Does the change require QA team to:

• Review automated tests?
• Execute manual tests?
• Provide feedback about the PR?

Up-port

TODO: link the develop-3.0.0 up-port PR, or state if not needed (does the same code-coverage.yml structure exist on develop-3.0.0?).

Backports

TODO: link any backport PR (e.g. develop), or state if not needed.

🤖 Generated with Claude Code

[codecov-github-com]

Codecov Report

All modified and coverable lines are covered by tests ✅

@@                Coverage Diff                @@
##           develop-2.0.0    #4101      +/-   ##
=================================================
+ Coverage          66.40%   73.87%   +7.46%     
=================================================
  Files                163      172       +9     
  Lines              24999    28013    +3014     
=================================================
+ Hits               16601    20695    +4094     
+ Misses              8398     7318    -1080     

Flag	Coverage Δ
NGOv2_project_testproject_ubuntu_trunk	73.66% <ø> (?)
NGOv2_ubuntu_trunk	66.43% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 67 files with indirect coverage changes

Components	Coverage Δ
com.unity.netcode.gameobjects	73.87% <ø> (+7.46%)	⬆️

ℹ️ Need help interpreting these results?

[EmandM]

Do you mind using the pinnedTrunk variable we have in project.metafile?

Occasionally trunk breaks our tests so we have a pinned "safe" version for PRs. We update the pinned version fairly regularly. Our nightly and weekly tests run on actual trunk.

[unity-nikos]

Fixed in ce72070

[unity-nikos]