Context
Changes to the Services drop-down menu tend to break other tests because our navigation targets heavily depend on the UI for navigation. Over time, this has become burdensome to maintain, as the targets need to be reworked every time we update the UI. 

Proposed Solution

As outlined in https://redhat-internal.slack.com/archives/C69UN1L4E/p1741192867432179, we would like to provide a set of "stable" nav targets for downstream IQE plugins. This way, the UI tests of other QEs don't break whenever we re-work the Services dropdown menu navigation.

Testing focused on the services menu drop-down will still exist. This merely unencumbers other UI tests from using the services menu navigation targets and makes their tests less prone to breakage when we rework the UI.

AC

• Update the platform_ui plugin to provide nav targets that use URL-based nav only (no interaction with the services menu UI)
• Add tests to confirm that the URL-based nav targets are operational
• Once the changes are ready, inform other QEs these nav targets are available.
•  

Note: Any associated refactoring/rework of the services drop-down menu tests will be covered in another ticket.