feat: allow using components in navigation bar

[userquin]

✔️ I need to add an example/test...

closes #3998

[userquin]

We should also add fly, maybe including mode type: type Mode = 'screen' | 'fly' | undefined or type Mode = 'screen' | 'fly' | 'navbar'

[userquin]

@brc-dd same component in multiples places, no makes sense, do we need the new mode prop? maybe not, since we should always have screen in screen menu (we'll need to add screen prop when custom component in root, check last screenshot)

[brc-dd]

Do we need some option to move component to flyout in medium viewports? Inside this thing:

(it might make things more complicated though, we can probably support that later?)

[userquin]

I guess there is no need, fly will be used when the custom component is not a root child in the navbar entry. If the custom component is in the root navbar, VP will not use fly (will use media query bp to collapse or expand the full navbar)