Fix namespace null bug for token projects table

What does this MR do and why?

Token projects table blows up when a user adds a project from a different namespace to their allowlist. This is because the API returns null for the namespace and we are trying to access properties that do not exist. This is a quick fix to get the app back up and running for this special use-case. A more permanent fix is figuring out why namespace is null for this use-case as it most likely should not be.

Screenshots or screen recordings

James recorded an example of this bug that can be found here https://youtu.be/4ehlxknq5Cw

Error

Example response when error occurs

How to set up and validate locally

1. Project > CI/CD > Token Access
2. Add project to allowlist that your current user/namespace does not have access too

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.