[tools] refactor gdad version param, update TypeDoc and TS

[Simek]

Why

It looks like the version parameter in gdad command from Expo Tools is a bit confusing for people, let's refactor it.

How

This PR refactors the gdad command, changes the version parameter to sdk, adds the output path validation with an helpful (I hope) error.

I have also bumped TypeDoc and TypeScript dependencies in tools. The changes in JSON files are only related to the new features, which added qualifiedName and package for some of the references:

• https://github.com/TypeStrong/typedoc/releases/tag/v0.22.11

Test Plan

The changes have been tested by recompiling and running Expo Tolls locally. Compilation do not output any new warning/errors after bumps.

I have also checked, that et gdad --sdk executed with invalid parameter value results in error:

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• This diff will work correctly for expo build (eg: updated @expo/xdl).
• This diff will work correctly for expo prebuild & EAS Build (eg: updated a module plugin).

[tsapeta]

Looks good, thanks. Although I'm not a big fan of upgrading deps on each occasion and so many docs data as well.

[Simek]

Although I'm not a big fan of upgrading deps on each occasion

FYI, I have upgraded the TypeDoc only initially, since this PR involved working with its code anyway, but this result in warning that current used TS version might not support newly added feature. Additionally I have saw this PR lately (#17387), so the TS bump is on the schedule for workspace. Tools are detached, so I thought that I have kill two birds with one stone. 😛

and so many docs data as well.

This is out of our control IMO, the reason why I have updated the files is that I want to avoid the confusion for someone who updates the TSDoc and want to regenerate data file to test the rendering on the docs side and after running et gdad instead of seeing one JSON changed for edited package they will see the list of several packages, and have no clue why they have been changed.

Also, as you know, I'm still the advocator of adding/hooking up JSON files regeneration into the package build process, which should also help/streamline the data generation. However bumping TypeDoc probably will always require the manual regeneration. 😅

[barthap]

I like it, this is gonna make me stop forgetting the v prefix when specifying the version 😉