Synthetic enum types hypothetically could miss deprecated/experimental flags

[joffrey-bion]

Enums that are declared inline in some parameters are extracted into separate named types as a workaround for ChromeDevTools/devtools-protocol#244.

During the extraction process, we should propagate the deprecated and experimental status from the parameter or the containing event/command/type to the extracted enum type.

If the enum is used in both deprecated and non deprecated declarations, it means the enum itself is still maintained and can be considered non-deprecated (it just happens to be used in a deprecated declaration). Same for experimental enums.

Note: currently no extracted enum is affected by this.