NextJS better way to handle navigation

[TheCodeDestroyer]

There seem to be a lot of issues with Tabs, Listbox, and some other components not respecting the navigation prop. It gets fixed, and after some versions, the issue comes back. I have seen this issue specifically with Tabs a year ago, then in v2.8 canary, which was fixed in some canary version. Now, in v2.8.1, it doesn't work again for Tabs.
Also, using push to navigate seems to remove some benefits that the NextJS Link component brings, like prefetching of routes. Would it maybe make sense to rethink HeroUIProvider and perhaps give us an option to provide a base anchor component instead of the navigate prop?

There are a lot of issues with this problem that keep coming back:

• [BUG] - Tabs component's href attribute hard reloading after moving from nextui to heroui #4598
• [BUG] - NextUIProvider navigate stills not being called #3572
• [BUG] - Page reload (without using a router) when clicking on a tab with href #5379
• [BUG] - LINK Reloaded page #5178
• [BUG] - DropdownItem routing don't work as expected #3219
• etc.