Fix reusing project-codes gets 404/undefined from GQL cache

[myieye]

Fixes #1051

It does actually seem to be the case that GQL caching was the problem here (even though I bumped into some weird behaviour in our awaitedQueryStore that I thought was the root of the issue).

I've opened a discussion In the hopes of finding a slightly more elegant solution, but I'm doubtful 🤷. So, for details see that discussion or the many comments in this PR.

There are several bonus fixes in this PR:

• Text ellipsis truncating wasn't working everywhere, so I fixed and standardized it
• Project tiles became very ugly with the dev tools open. And they still might on small screens, but meh. That's not as bothersome.
• The error page was no longer working well for 404 errors. It would start fine, but then immediately update using the 200 from the page load.

[github-actions]

UI unit Tests

12 tests   12 ✅  0s ⏱️
 4 suites   0 💤
 1 files     0 ❌

Results for commit 493018d.

♻️ This comment has been updated with latest results.

[myieye]

@hahn-kev You were right, of course 😉. I was totally on the wrong track. I didn't realize that we were excpliticly caching null.

I ended up adding 2 fixes...either one would actually fix this specific error. The reason I included both is:

1. Pausing the store prevents 2 meaningless and undesireable HTTP requests. So, it just makes sense.
2. Never caching nulls protects us from any other scenarios that might lead to a null project getting cached (e.g. navigating to a project that doesn't exist or was just deleted), which could lead to the same original error

[hahn-kev]

I want to get this merged since we have people actively seeing this error. But I also want to have an automated test for this since we've had project deletion broken before. Do you want to do it in this PR or another one?

[hahn-kev]

just one minor request, feel free to merge it then.