Core should be able to instantiate Parsoid with appropriate SiteConfig/PageConfig/DataAccess without loading Parsoid as an extension. That is, something like the following should be possible w/ just Parsoid 'library' code and core support:
```
$siteConfig = $services->get( 'ParsoidSiteConfig' );
$dataAccess = $services->get( 'ParsoidDataAccess' );
$pageConfigFactory = $services->get( 'ParsoidPageConfigFactory' );
$pageConfig = $pageConfigFactory->create(
$title, $user, $revId, $test->wikitext, $langCode
);
[...]
$parsoid = new Parsoid( $siteConfig, $dataAccess );
$out = $parsoid->wikitext2html( $pageConfig, [ ... ]);
```
Caveats:
* This effectively freezes the interfaces in `Parsoid/src/Config/*` and the `Parsoid` class. Making changes to these after the move will requires a somewhat elaborate dance: the change must land in Parsoid without breaking core, then Parsoid needs to be released to composer with an appropriate version bump, then a corresponding change to core can be made simultaneous with a version bump in core's `composer.json`, then finally any backwards-compat code in Parsoid can be removed, then mediawiki-vendor's `composer.json` needs to be updated for the next train.
* Because of this elaborate dance, changes to the service configuration to make it more DI friendly will be done in the Parsoid repo before the move, so that they can be reviewed in context and released w/o a dance.
* It's not clear exactly which services are going to be exported for external use long-term; the ParsoidSiteConfig/ParsoidDataAccess/PageConfigFactory/etc services should probably be marked `@unstable` for now. (eg Parsoid's `PageConfig` has substantial overlap with the existing `ParserOptions` class.)
* Similarly, there might be a `ParsoidFactory` service exported temporarily, but the long term plan is not to expose this as a separate services; instead the existing `ParserFactory` service will start returning `ParsoidParser` objects at some point (T236812). So any `ParsoidFactory` service should again be marked unstable/temporary.
* The code in `Parsoid/extension/src/Rest/*` is not included in this task: it's not clear whether we will expose the current Parsoid REST API in core, or replace it with a new API. As such, we might still do a copy-paste of `Rest/*` into VisualEditor for the 1.36 release, as we did in T248343 for 1.35, since the RESTBase replacement (Txxxxx) isn't likely to be complete until 1.37 at the earliest. But at least 1.36 will copy *less* code into VE than 1.35 did.
The deadline for this task is the 1.36 release, although hopefully it will be done in the next month or so, since both T254181 and I6d9999b315def616e973daca0b7d544e502c7212 will benefit from it.