fix: address issues with release of react 19 (#898)

React 19 removes the global JSX namespace - replace with React.JSX which works with both React 19
and 18. Additionally address type error with new versions of react-router-dom's `navigate` function
returning a promise.

Fixes #895
Fixes #896

packages/cloudscape-react-ts-website/samples/cloudscape-react-ts-website/src/layouts/App/index.tsx.mustache

@@ -78,7 +78,7 @@ const App: React.FC = () => {
           splitPanelSize: undefined,
           splitPanelPreferences: undefined,
         });
-        navigate(e.detail.href);
+        void navigate(e.detail.href);
       }
     },
     [navigate],

packages/cloudscape-react-ts-website/samples/cloudscape-react-ts-website/src/pages/Home/index.tsx.mustache

@@ -26,7 +26,7 @@ import { useNavigate } from "react-router-dom";
 const Home: React.FC = () => {
   {{#hasApis}}
   const navigate = useNavigate();
-  useEffect(() => navigate("/apiExplorer"), []);
+  useEffect(() => void navigate("/apiExplorer"), []);
   {{/hasApis}}
 
   {{#typeSafeApis.0}}

packages/type-safe-api/scripts/type-safe-api/generators/typescript-react-query-hooks/templates/clientProvider.ejs

@@ -48,7 +48,7 @@ export const <%- service.className %>ClientProvider = ({
   context = <%- service.className %>DefaultContext,
   <%_ } _%>
   children,
-}: <%- service.className %>ClientProviderProps): JSX.Element => {
+}: <%- service.className %>ClientProviderProps): React.JSX.Element => {
   return (
     <QueryClientProvider client={client}<% if (!metadata.queryV5) { %> context={context}<% } %>>
       <<%- service.className %>ClientContext.Provider value={apiClient}>