gentype: support Jsx.element in addition to React.element

The type Jsx.element can show user-side in ppx V4 (at least), and affects gentype too.
It special-cases `React.element`, and needs to then special-case `Jsx.element` too.

Fixes #6807

# Conflicts:
#	CHANGELOG.md

Author: cristianoc

CHANGELOG.md

@@ -17,6 +17,7 @@
 - Fix location of let bindings with attributes. https://github.com/rescript-lang/rescript-compiler/pull/6791
 - PPX v4: mark props type in externals as `@live` to avoid dead code warnings for prop fields in the editor tooling. https://github.com/rescript-lang/rescript-compiler/pull/6796
 - Fix issue where optional labels were not taken into account when disambiguating record value construction. https://github.com/rescript-lang/rescript-compiler/pull/6798
+- Fix issue in gentype when type `Jsx.element` surfaces to the user. https://github.com/rescript-lang/rescript-compiler/pull/6808
 
 # 11.1.1
 

jscomp/gentype/TranslateTypeExprFromTypes.ml

@@ -215,7 +215,8 @@ let translateConstr ~config ~paramsTranslation ~(path : Path.t) ~typeEnv =
     {dependencies = []; type_ = EmitType.typeReactEventMouseT}
   | ( ( ["React"; "element"]
       | ["ReactV3"; "React"; "element"]
-      | ["ReasonReact"; "reactElement"] ),
+      | ["ReasonReact"; "reactElement"]
+      | [("Pervasives" | "PervasivesU"); "Jsx"; "element"] ),
       [] ) ->
     {dependencies = []; type_ = EmitType.typeReactElement}
   | (["FB"; "option"] | ["option"]), [paramTranslation] ->