Build Tooling: Further improve asset file produced by Webpack for each entry point

[gziolo]

In #17298 we started to generate asset files for the WordPress packages in PHP format with the list of all dependencies and stable version for each file which updates when it's source code changes.

There are some follow-up tasks which we can work on to further improve developer experience as summarized by @nerrad in #17298 (review):

Summarizing what can be iterated on in future pulls:

• flagging what assets have translations (likely can be done by detecting @wordpress/i18n as a dependency)
• generating/returning the handle to use for registering the asset (essentially that is already the case for the dependency arrays)
• potentially introducing a new asset php api for registering assets using these generated files (wp_register_asset?).

[jrchamp]

The asset file produced doesn't appear to generate all dependencies when using the wp.data and other globals as described in the documentation. #17423

[gziolo]

We can close it now since all those points were resolved in WordPress core and the last item is going to be tackled separately.