Consider publishing wallet-dashboard utilities (hooks/constants) as part of the TS SDK

## Description:

While trying to build a Next.js template based on the [wallet-dashboard](https://github.com/iotaledger/iota/tree/develop/apps/wallet-dashboard) app, we noticed that several imports from @iota/core are actually TypeScript [rewrites](https://github.com/iotaledger/iota/blob/f4cc8e807935e093607fa8c06db2ddacf1a1fe52/apps/wallet-dashboard/tsconfig.json#L21) that live only inside the IOTA monorepo and are not exported in the published [@iota/core](https://www.npmjs.com/package/@iota/core) package on npm.

This makes it difficult to reuse components such as hooks and constants in external applications or templates.

⸻

Affected internal paths:
• [apps/core/src/hooks](https://github.com/iotaledger/iota/tree/develop/apps/core/src/hooks)
• [apps/core/src/constants](https://github.com/iotaledger/iota/tree/develop/apps/core/src/constants)

⸻

Expected behavior:

It would be useful if these utilities (hooks and constants) could be exported via @iota/iota-sdk , so external projects and templates can rely on them without duplicating code or importing the whole monorepo as a Git dependency.