fix(preprod): Fix project slug/id confusion in a few places

[chromy]

No description provided.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[trevor-e]

Bit confused by this change, won't it make it more confusing to get the id vs slug right? 😆

[sentry]

Bug: The component incorrectly uses ProjectsStore.getById() with a project slug, causing project to be undefined. The removal of optional chaining from project.slug will cause a crash.
_{Severity: CRITICAL}

Suggested Fix

In buildDetailsHeaderContent.tsx, change the project lookup to use the correct method for a slug. Replace const project = ProjectsStore.getById(projectId); with const project = ProjectsStore.getBySlug(projectId); to ensure the project is found correctly.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location:
static/app/views/preprod/buildDetails/header/buildDetailsHeaderContent.tsx#L206

Potential issue: In `buildDetailsHeaderContent.tsx`, the `project` object is fetched
using `ProjectsStore.getById(projectId)`. However, the `projectId` prop it receives from
the parent component (`buildDetails.tsx`) is actually a project slug string from the
URL, not a numeric ID. This causes the `getById` lookup to fail, making the `project`
variable `undefined`. The removal of optional chaining in the new code at line 206 means
that the attempt to access `project.slug` will result in a `TypeError`, causing the
application to crash when rendering the build details page.