Adapt work package lists for semantic identifiers

[akabiru]

Ticket

https://community.openproject.org/work_packages/73717

Important

NB: Take note of the following subsequent work not covered in this PR

• Use displayId in work package URLs for semantic identifier routing #22733
• Use displayId in stateful navigation and fix semantic ID state management #22739

What are you trying to accomplish?

Use the new formattedId property consistently across all work package list and card views, replacing hard-coded #{{ wp.id }} patterns that would show the numeric PK instead of the semantic identifier.

What approach did you choose and why?

PR #22704 added displayId and formattedId to WorkPackageBaseResource. formattedId conditionally prefixes # only for classic numeric IDs — semantic identifiers like PROJ-42 are self-describing and render without a prefix, matching Jira's convention.

This PR updates all remaining display sites to use them:

• Card view, relation rows, single view header, and quickinfo macro — switched from #{{ wp.id }} to {{ wp.formattedId }}
• Destroy modal, in-app notifications, and timer modal — same pattern, these were still using #{{ wp.id }} or '#' + workPackage.id
• Display field modules (WorkPackageDisplayField, LinkedWorkPackageDisplayField) — added wpFormattedId getter with semantic ID support: when the linked resource is loaded, it reads displayId and applies the same conditional hash logic; otherwise it falls back to hash-prefixed numeric ID from the self-link href

This means every place that shows a work package identifier to users now goes through formattedId, so PROJ-42 renders correctly in semantic mode and #123 in classic mode, with no per-view conditional logic.

Merge checklist

• Added/updated tests
• Added/updated documentation in Lookbook (patterns, previews, etc)
• Tested major browsers (Chrome, Firefox, Edge, ...)