…#26343)

# Why

Update TypeDoc to the latest release to keep up to day and officially
support package source build with TS 5.2+.

All data files have been changed, since TypeDoc removed on of legacy the
entry Kind enum values (`ObjectLiteral`) which caused a shift of
existing values after it.

# How

Update TypeDoc to the latest version, rewrite TypeDoc Application calls
execution, update Docs snapshot and unit tests to match the data.

Unfortunately, the data generation command outputs not valid for our use
case warning due to TypeStrong/typedoc#2440,
but it doesn't matter in our case due to using the JSON data only, and
custom renderers, which can handle both comment structures correctly, so
those warning can be ignored. We can alter source comments in the
future, when stable SDK 50 will be releases to avoid shipping large
amount of changes in preview/RC stage.

> [!important]
> No backport of `expo-assets` data for SDK 50 has been made due to
#26310, which probably did not become part od SDK 50, but if will land,
we will need to backport the package data, since the structure and
exported fields have changed.

# Test Plan

The changes have been reviewed locally. Reference doc pages contains a
full, and expected data. All lint checks and tests are passing.

…expo#26343)

# Why

Update TypeDoc to the latest release to keep up to day and officially
support package source build with TS 5.2+.

All data files have been changed, since TypeDoc removed on of legacy the
entry Kind enum values (`ObjectLiteral`) which caused a shift of
existing values after it.

# How

Update TypeDoc to the latest version, rewrite TypeDoc Application calls
execution, update Docs snapshot and unit tests to match the data.

Unfortunately, the data generation command outputs not valid for our use
case warning due to TypeStrong/typedoc#2440,
but it doesn't matter in our case due to using the JSON data only, and
custom renderers, which can handle both comment structures correctly, so
those warning can be ignored. We can alter source comments in the
future, when stable SDK 50 will be releases to avoid shipping large
amount of changes in preview/RC stage.

> [!important]
> No backport of `expo-assets` data for SDK 50 has been made due to
expo#26310, which probably did not become part od SDK 50, but if will land,
we will need to backport the package data, since the structure and
exported fields have changed.

# Test Plan

The changes have been reviewed locally. Reference doc pages contains a
full, and expected data. All lint checks and tests are passing.