Fix search route error catch handler result being discarded

[J8118]

Summary

In the skeleton template's search.tsx loader, the .catch() handler on searchPromise returns a fallback value, but this return value is discarded because return await searchPromise on line 33 awaits the original promise, not the one with the catch handler attached. .catch() creates a new promise chain — the original promise still rejects.

If searchPromise rejects, two things happen:

1. The .catch() handler logs the error and returns a fallback (but this value goes nowhere)
2. await searchPromise throws, resulting in a 500 error

File changed:

• templates/skeleton/app/routes/search.tsx (lines 28-33)

Before:

searchPromise.catch((error: Error) => {
  console.error(error);
  return {term: '', result: null, error: error.message};
});

return await searchPromise;

After:

return await searchPromise.catch((error: Error) => {
  console.error(error);
  return {term: '', result: null, error: error.message};
});

[fredericoo]

nice find - the `.catch()` return value was being discarded, so the error fallback never actually reached the caller. the fix correctly chains the catch.

since this is a skeleton template change, it needs a triple changeset bump per our repo rules. could you add one?

```md

"skeleton": patch
"@shopify/cli-hydrogen": patch
"@shopify/create-hydrogen": patch

Fixed search route error handling so search errors are gracefully handled with a fallback instead of causing unhandled rejections.
```

cheers!

[J8118]

Done — just pushed the triple-bump changeset