fix(filesystem): fix file dialog location input navigation

[ndoschek]

What it does

Resolves GH-17664

• compare the requested location against the live current location in trySetNewLocation instead of a cached lastUniqueTextInputLocation
• the cached value went stale after navigating via the Up/Back/Forward/Home buttons or the tree, silently blocking navigation to a previously visited path typed into the location input
• remove the now-unused lastUniqueTextInputLocation field
• add regression tests for trySetNewLocation

How to test

1. Start the example browser application
2. Open a file dialog (e.g. File > Open... or Open Workspace...).
3. Click the edit (pencil) icon to switch the location bar to text input.
4. Type an absolute path, e.g. /home, and press Enter. The dialog navigates to /home.
5. Move to a different folder without using the text input, for example click the Navigate Up button (or Back), or double-click a folder in the tree.
6. Click the edit (pencil) icon again, type the same path as in step 3 (/home), and press Enter.
7. Verify that everytime you enter a (valid) path manually, it is accepted and the file dialog navigates there

Follow-ups

Breaking changes

• This PR introduces breaking changes and requires careful review. If yes, the breaking changes section in the changelog has been updated.

Attribution

Contributed on behalf of STMicroelectronics

Review checklist

• As an author, I have thoroughly tested my changes and carefully followed the review guidelines
• User-facing text is internationalized using the nls service (for details, please see the Internationalization/Localization section in the Coding Guidelines)

Reminder for reviewers

• As a reviewer, I agree to behave in accordance with the review guidelines