[BUG]: imperfect type definitions around graph export features

[fujidana]

Description

I found the following imperfect definitions in type definitions Plotly introduced recently (v4.0.0?), around toImage(), downloadImage() and config.toImageButtonOptions. This will hinder using these functions/option for TypeScript users (like me).

• Lack of full-json export format. A graph can be exported as JSON probably since v1.53.0 (see CHANGELOG.md or add format "full-json" to Plotly.toImage and Plotly.dowloadImage #4593) but this feature was not documented until very recently (docs: Add 'full-json' docs, examples graphing-library-docs#471).
• Lack of imageDataOnly option. This option is also very recently documented here.
• Some properties being set as required. The properties of the second parameter in toImage() and downloadImage() should be all optional. Currently some are required.

Can I send a PR for these? The PR won't include changes on executable code in JS; it will only modify *.d.ts files and maybe docstring parts in JS files.

[camdecoster]

I was just looking at this as a result of your docs PR. Updating the hand written types is a good first step, but I'm wondering if we should update the schema and then generate the types from that. What do you think?