[COMMS-915] Count work package summary versions from target_versions

[akabiru]

COMMS-915

The work package summary page counted versions through the deprecated version_id column, which only ever holds a work package's first target version. Work packages assigned to several target versions were therefore counted under a single version, and the totals no longer matched the filtered list a cell links to (that drill-down already filters on target_versions). The summary now counts through the work_package_versions target associations, so each work package is counted under every version it targets and the counts agree with the list behind them. The section heading also follows the multiple versions feature flag, reading "Target versions" when it is on, matching how the rest of the UI labels the field.

Work package #42 targets both 1.0.0 and 2.0.0. Before, it was counted only under 1.0.0, so 2.0.0 read 3; after, it is counted under both and 2.0.0 reads 4.

Before

After

[github-actions]

Warning

Flaky specs

• rspec ./spec/features/roles/report_spec.rb[1:1]
• rspec ./spec/features/roles/report_spec.rb[1:2]
• rspec ./spec/features/roles/report_spec.rb[1:3]
• rspec ./spec/features/search/search_spec.rb[1:4:1]

🤖 Ask Copilot to investigate

Copy the prompt below into a new comment on this PR to delegate the investigation to GitHub Copilot. It will look into the flakiness and open a separate pull request with you as reviewer.

@copilot The following spec(s) are flaky in CI (first seen on PR #24400, linked for reference only):

- `rspec ./spec/features/roles/report_spec.rb[1:1]`
- `rspec ./spec/features/roles/report_spec.rb[1:2]`
- `rspec ./spec/features/roles/report_spec.rb[1:3]`
- `rspec ./spec/features/search/search_spec.rb[1:4:1]`

Treat this as a standalone task, unrelated to PR #24400. Create a new branch from origin/dev and open a new pull request targeting dev — do not stack it on PR #24400 or reuse that branch.

Follow the playbook in docs/development/testing/handling-flaky-tests/README.md to find the root cause and fix the underlying race — do not skip, delete, or weaken the spec to make it pass; disabling is a last resort per the playbook, and only with a bug ticket. Verify the fix by running the spec(s) repeatedly (e.g. `script/bulk_run_rspec --run-count 10`).

If you cannot reproduce the flake or are not confident in a fix after reasonable investigation, do not fabricate a change or skip the spec to force CI green. Instead, leave the pull request in draft and document what you tried, the suspected cause, and any leads in its description, then assign @akabiru to take over.

Once the fix is verified, title the PR after the spec(s) it fixes, and use the PR description to explain the root cause, how the change resolves it, and the before/after results. Label the PR `flaky-spec`, assign @akabiru, and request a review from @akabiru.
On every commit, set @akabiru as the sole co-author with a `Co-authored-by:` trailer (use their GitHub no-reply email so it links to their account), so it is traceable who dispatched the fix.