Issue with recent WP versions (6.4, 6.5) at circleci, failing due to WP_REST_Revisions_Controller not found.

[claimableperch]

Describe the bug
In one or two plugin repositories our automated tests were failing during container 'start' due to bad 'require' from wp-settings.php
The code was obviously not what we were intending to be used and was presumably sourced via cURL from a wordpress tgz.
Obviously our composer vendor directory was fine, so I hacked this alteration which might fit smoothly in (#141).

To Reproduce
Steps to reproduce the behavior:

1. Plugin repo.
2. Use { wp : { plugins: ['./'] } } in cypress config repository with a complex autoload geometry.
3. Bring up 'npx wp-cypress start' in automated testing.
4. Scratch your head because 'start' fails unless SSH is active ('Re-run with SSH').
5. Use wp-cypress from PR#141 (claimableperch/wp-cypress#v0.9.1 is release/1.0.0 from this repo with feat(vendor-sync): use specified directory instead of curl and zip files #141 and feat(environment): allow to specify container runtime environment variables #140 added to it) with { wp: { version: 'path-to-wordpress' } } in the cypress.config.js
6. See your chosen source work without a hitch.

Desired behavior
Source from your chosen wordpress directory (e.g. './vendor/wordpress/wordpress') makes its way into the container.
This also helps with debugging if using wp-cypress as your dev-env.