Update react-contexify to 6.0.0

[benwolfram]

Problem:
As apart of modernizing and updating context menus, bumping react-contexify to the latest version following their migration guide.

Fix:'

This PR fixes keyboard navigation for the context menu, however, events are still bubbling up to the editor. Will look at this next.

• Bumping to version 6.0.0

• Changing how show is called, with the event

• Updating classes and redoing the styles

• Removing explicit 28px heights

• Using onVisibilityChange

• Typescript type fixes

• Removing the existing patch?

  • I am not sure what this is even, but I realized it was tied to 5.0.0 version, so it seemed irrelevant now. I assume there is a good reason why it exists, so please let me know if this needs to be redone for v6 and how that is done

Manual Tests:
I hereby swear that:

• I opened a hydrogen project and it loaded
• I could navigate to various routes in Preview mode

Relates to #5643

[benwolfram]

As noted in PR description, let me know if (and how) this needs to be re-created for v6.

[github-actions]

Try me

[relativeci]

#12700 Bundle Size — 62.24MiB (~-0.01%).

b0a37dc(current) vs 6339ece master#12690(baseline)

Warning

Bundle contains 51 duplicate packages – View duplicate packages

Bundle metrics   3 changes 1 improvement

	Current #12700	Baseline #12690
Initial JS	45.31MiB(~-0.01%)	45.32MiB
Initial CSS	0B	0B
Cache Invalidation	26.2%	22.06%
Chunks	30	30
Assets	33	33
Modules	4293	4293
Duplicate Modules	521	521
Duplicate Code	31.79%(+0.03%)	31.78%
Packages	448	448
Duplicate Packages	51	51

Bundle size by type   2 changes 2 improvements

	Current #12700	Baseline #12690
JS	62.23MiB (~-0.01%)	62.23MiB
HTML	11.16KiB (-0.32%)	11.2KiB

---

Bundle analysis report Branch context-menu-update Project dashboard

[github-actions]

Performance test results:

[benwolfram]

Would love some assistance on:

• What are / is the difference between Test Editor Shard 1 vs. 2
  • I think # 1 is equivalent to pnpm run test so I am able to run that locally and debug (this is just failing the flaky/unrelated test)
  • How I can run/debug the # 2 test suite locally
• Getting performance tests fixed

[benwolfram]

The "try me" version doesn't seem to be working at all 😕, but it definitely does locally for me.

[balazsbajorics]

@benwolfram are we tracking this? we should really kill this localXHack!
this was meant as a temporary fix in a demo deadline push a few weeks ago, simply put here because we only had five minutes to fix the offset.

[benwolfram]

Nope, this wasn't on my todo list. I am not even sure what it is tbh, but I can take a look here soon in a future PR, as I was intending to wrap work on Context Menu.

[balazsbajorics]

left some minor feedback but mostly looks good!

[balazsbajorics]

it looks like this PR broke The navigator component picker context menu Karma tests