Test/navbar desktop coverage

[Sparshagarwal29]

Description

This PR improves test coverage for the NavbarDesktop component.

I added a few focused tests that exercise real user interactions (opening the user menu, navigation links, GitHub link, and auto-sync UI) rather than relying on snapshot-only coverage.
A very small, non-functional tweak was made in NavbarDesktop to make these behaviors easier to test. No runtime behavior or logic was changed.

• Fixes: Add frontend test suites/cases for src/components/HomeComponents/Navbar #302

Checklist

• Ran npx prettier --write . (handled via pre-commit hook)
• Ran gofmt -w . (not applicable)
• Ran npm test
• Added unit tests, if applicable
• Verified all tests pass
• Updated documentation, if needed

Additional Notes

This PR focuses on improving interaction-based test coverage for NavbarDesktop.
Some UI branches depend on third-party UI primitives and internal state transitions,
which are intentionally not over-mocked to keep tests maintainable and realistic.

Before

After

[github-actions]

Thank you for opening this PR!

Before a maintainer takes a look, it would be really helpful if you could walk through your changes using GitHub's review tools.

Please take a moment to:

• Check the "Files changed" tab
• Leave comments on any lines for functions, comments, etc. that are important, non-obvious, or may need attention
• Clarify decisions you made or areas you might be unsure about and/or any future updates being considered.
• Finally, submit all the comments!

More information on how to conduct a self review:
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request

This helps make the review process smoother and gives us a clearer understanding of your thought process.

Once you've added your self-review, we'll continue from our side. Thank you!

[its-me-abhishek]

Can it be further improved? @Sparshagarwal29

[Sparshagarwal29]

Can it be further improved? @Sparshagarwal29

Thanks for the review.
Some remaining uncovered paths are tightly coupled to Radix Dialog/Dropdown behavior and async side effects (export/delete confirmation flows). Covering those reliably would likely require either refactoring the component to expose test seams or introducing heavier mocking, which I avoided in this PR to keep the tests stable and maintainable.

If you’d like, I can follow up with focusing on one of those flows (for example, delete confirmation or export actions), or refactor the component slightly to improve testability.