Open an Issue through its canonical Team route

[mrboxs]

This was generated by AI during triage.

What to build

Implement the canonical Issue detail read path for the Core Issue Loop. A Workspace Member should be able to open an Issue from the Team issue list at /:workspaceSlug/team/:teamKey/issues/$issueKey and see the Issue's core fields.

The route and API must resolve workspaceSlug, teamKey, and issueKey server-side instead of trusting client-provided IDs.

Acceptance criteria

• /:workspaceSlug/team/:teamKey/issues/$issueKey renders the canonical Issue detail route.
• issue.getByKey resolves Workspace, Team, and Issue by slug/key values server-side.
• The detail page shows title, description, Workflow Status, assignee, creator, priority, estimate, due date, created timestamp, and updated timestamp.
• Unknown Issue keys return an authorization-safe not found response.
• Issue keys from another Workspace return the same authorization-safe not found/denial behavior.
• Issue keys from another Team do not render under the wrong Team route.
• The Team issue list links each Issue to the canonical detail route.
• Loading and error states are implemented for the detail route.

Blocked by

• Create the first Issue with a transactional team issue key #45

[linear-code]

BOXS-47