feat: Move home bookmark to a separate button on the top bar

[AdityaHegde]

• Move the home bookmark out of bookmarks dropdown.
• The button should be available even when there is no home bookmark. Should take the user to blank dashboard, i.e. a url without any params.
• Fix issue where the button doesnt apply the state due to race condition. Not worth fixing on main's code since there are changes coming in APP-59: feat: Restore certain explore user state across page loads. #6964
• Figure out what we will show on a shared url and rill-dev. We will not show this for shared-url and rill-dev.

Checklist:

• Covered by tests
• Ran it and it works as intended
• Reviewed the diff before requesting a review
• Checked for unhandled edge cases
• Linked the issues it closes
• Checked if the docs need to be updated
• Intend to cherry-pick into the release branch
• I'm proud of this work!

[ericpgreen2]

Let's get a Product review from @jkhwu. A few UXQA I see:

1. The Home button does not have the same hover state as the buttons it's next to
2. Should the Home button be disabled when either there's no Home bookmark or you're currently viewing the Home state? Disabled + tooltip to explain why.
3. It feels a bit off that the "Bookmark your current view as home" action exists in a dropdown that's anchored off a different button. Maybe, when there's no Home bookmark, the Home button should open a dropdown menu with the prompt?(CC @jkhwu)

Looks like the Home bookmark e2e test needs to be updated.

[AdityaHegde]

Thanks @ericpgreen2

1. Ya lemme fix that.
2. We can disable when the current state is equal to the button's link. But we need it to take the user to blank dashboard when there is no home bookmark. This is per requirement, cc @mindspank
3. Will defer to @jkhwu
4. Will fix the tests.

[ericpgreen2]

Code looks good. I'll defer to @mindspank to approve as product owner, as I have reservations about this:

It feels a bit off that the "Bookmark your current view as home" action exists in a dropdown that's anchored off a different button.

[ericpgreen2]

Design-wise, IMO we need to make clear the difference between these two menu items. They look "equal", yet one should be clearly a navigation action and one should clearly be not. A couple ideas:

1. Adding a separator between the menu items
2. Editing the "Home" copy to be "Go to home"
3. Moving the "Go to home" menu item above the other, since it'll be the more common action.

@jkhwu, any other thoughts on this?

[ericpgreen2]

We should use the same term from Figma: "active"