Release v22.96.0

Added

• The Screenplay generator reads the application's react-router route table (<Routes>/<Route path element> declarations, or createBrowserRouter, createHashRouter and createMemoryRouter calls with literal route objects) and states navigation between screens: a menu item's navigate('/literal') becomes item <name> navigate to <Screen>, and a CommandDialog onSuccess navigation becomes the action's navigate to <Screen>. Required route parameters such as :id are bound with parameter id from literal "42", and a screen in another slice is referenced by its qualified name. See Generating a Screenplay. (#3203)
• Navigation is stated only when the destination is proven: the route table is the application's root table (it renders or creates the router, or it is the only file declaring routes), and exactly one known route can match the literal path. Ambiguous, computed, lazy, wildcard and nested route tables, <Link to>, relative navigation and navigation with options stay reported with SP0028. (#3203)