fix: make TS happy with explicit return

[jaredcwhite]

Description

The shared-helpers linter in the core Bloom repo was failing due to an implicit return in Seeds' useTimeout hook. This adds an explicit return so that the linter will be happy.

How Can This Be Tested/Reviewed?

I tested the fix in the local node_modules copy of ui-seeds and the shared-helpers Jest tests passed.

Checklist:

• [ ] I have added QA notes to the issue with applicable URLs
• [x] I have performed a self-review of my own code
• [ ] I have reviewed the changes in a desktop view
• [ ] I have reviewed the changes in a mobile view
• [ ] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have exported any new components
• [x] My commit message(s) and PR title are polished in the conventional commit format, and any breaking changes are indicated in the message and are well-described

[netlify[bot]]

✅ Deploy Preview for storybook-ui-seeds ready!

Name	Link
🔨 Latest commit	2e328ff904becedd65eb81f0e518e060cef57ae3
🔍 Latest deploy log	https://app.netlify.com/sites/storybook-ui-seeds/deploys/6567fce1ccfd250008a3d294
😎 Deploy Preview	https://deploy-preview-70--storybook-ui-seeds.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions[bot]]

:tada: This PR is included in version 1.12.1 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: