fix(fetchMenu): fallback to $fetch on client after hydration

[StirStudios]

Summary

• update fetchMenu flow to use a client-safe $fetch fallback after hydration
• keep server-side behavior unchanged while preventing client-side hydration path failures

Why

• resolves cases where hydrated client navigation can fail to retrieve menu data through the server-oriented path
• ensures menu requests continue to work consistently across SSR and post-hydration client execution

Scope

• targeted change in src/runtime/composables/useDrupalCe/index.ts
• no public API changes

Validation

• focused on hydration/menu-fetch behavior regression addressed by this patch

[fago]

sry for letting this lie so long. @StirStudios Could you clarify why this is needed? usually the menu-fetching should work just fine client-side as well + hydrate properly also?

[StirStudios]

This fails for us on a full page refresh when used in the admin menu — specifically within the user account menu.

Without this in place, the user menu breaks on full page refreshes.