Find next behaviour using the keyboard is inconsistent

### Apache NetBeans version

Apache NetBeans 28

### What happened

While editing code, I search for text using Ctrl-F, and replace text using Ctrl-H. When I press F3, it repeats the last of the two actions that was performed, which is inconsistent. In an older version of Netbeans (unfortunately, I cannot recall which version), it would always repeat Ctrl-F. Which is my expected behavior, and typical of other editors. I would expect a different hotkey to repeat the replace action.

Also, on the Edit menu, the Find Next is under the Find Selection menu item.

### Language / Project Type / NetBeans Component

Code editor

### How to reproduce

- Using the first paragraph of Lorem Ipsum in a text file as an example
- Go the the top of the file
- Press Ctrl-F and search for "velit" and it will find the word
- Close the search bar at the bottom by pressing Esc. This is the critical step.
- Navigate to the start of the paragraph
- Press F3
- Navigate to the start of the paragraph
- Press Ctrl-H
- Replace "in" with "un", but only do it once (Click Replace)
- Close the search bar at the bottom by pressing Esc. This is the critical step.
- Navigate to the start of the paragraph
- Press F3, now it is search for "un". It is not replacing, it is doing a normal search, but for the wrong thing.
- Navigate to the start of the paragraph
- Press Ctrl-F again and search
- If were now to close this and repeat the F3, it would revert to searching for "velit"

### Did this work correctly in an earlier version?

Apache NetBeans 24 or earlier

### Operating System

Window 11

### JDK

OpenJDK Runtime Environment 25.0.1+8-LTS

### Apache NetBeans packaging

Apache NetBeans platform

### Anything else

Happens every time

### Are you willing to submit a pull request?

Yes

Start in the NetBeans code editor by reproducing the Ctrl-F, Ctrl-H, Esc, and F3 sequence described in the issue, then inspect the Find Next action and its Edit-menu placement. Done means F3 consistently repeats the expected find behavior after either search action and Find Next is placed appropriately in the menu.

Written by the indexing model from the issue text.