[ts] migrate root test dir to project refs

[spalger]

While working on #98337 and exploring the possibility of colocating tests with plugins I'm running into an issue because the test/ project isn't using project refs. This change wasn't simple, it required that we stop using class expressions as the return value of Service/PageObject providers.

Unfortunately this is a pattern that we use throughout the FTR providers so I'm working on PRs that migrate us away from this pattern and to a new pattern where services extend a base FtrService class, which provides a constructor that exposes the other services via this.ctx.getService('...') and this.ctx.getPageObjects([...]). See the discussion here about other possibilities we considered and their trade offs: #99148 (comment)

This approach seems to have the fewest trade offs:

• pros
  • class is just exported from a module, which is a very TypeScript friendly move and integrates well
  • type signatures look good in editors (as opposed to POJOs which just list tons of methods as the signature)
  • class defines its own interface, no need to write separate interfaces or anything
  • using this.ctx.getService() to fetch other service handles mapping dependent types appropriately
• cons
  • we need to use this. to reference other services which were previously available without the prefix
  • the code changes required are numerous, even if they are mostly mundane

To help educate people of the change and to make review of this pretty massive API change more manageable I broke up the services into many smaller PRs which specific teams reviewed. This PR now includes all the PageObjects and a handful of remaining services in one final step as the conflicts caused by breaking the PR up were really hard to deal with and I think info about this change is starting to spread naturally.

Reviewers note

The vast majority of changes are just extracting classes from providers and remapping access to services/pageObjects to properties on this. Viewing the changes side-by-side and without whitespace will help you see the changes in this PR for just what they are.

[dmlemeshko]

One of the PRs failed with the error:

Error: retry.try timeout: TypeError: Cannot read property 'testSubjects' of undefined
    at getFn (test/functional/services/inspector.ts:230:17)
    at block (test/functional/apps/visualize/_vega_chart.ts:126:49)
    at runAttempt (test/common/services/retry/retry_for_success.ts:27:21)
    at retryForSuccess (test/common/services/retry/retry_for_success.ts:66:27)
    at RetryService.try (test/common/services/retry/retry.ts:31:12)
    at Context.<anonymous> (test/functional/apps/visualize/_vega_chart.ts:125:13)
    at Object.apply (node_modules/@kbn/test/src/functional_test_runner/lib/mocha/wrap_function.js:73:16)
    at onFailure (test/common/services/retry/retry_for_success.ts:17:9)
    at retryForSuccess (test/common/services/retry/retry_for_success.ts:57:13)
    at RetryService.try (test/common/services/retry/retry.ts:31:12)
    at Context.<anonymous> (test/functional/apps/visualize/_vega_chart.ts:125:13)
    at Object.apply (node_modules/@kbn/test/src/functional_test_runner/lib/mocha/wrap_function.js:73:16)

@spalger The fix was trivial 152bdda, but I wonder if TS can help us avoid similar usage in future?

[spalger]

@spalger The fix was trivial 152bdda, but I wonder if TS can help us avoid similar usage in future?

Unfortunately I don't think there is anything that TS can do to help us here. this context is tricky, there isn't any way to require that class methods be called with the correct this context, but at least it's stable so those tests would never pass or make it out of a PR, so I'm not super worried about it.

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[elasticmachine]

Pinging @elastic/kibana-qa (Team:QA)

[LeeDr]

LGTM - code reviewed only.

[brianseeders]

LGTM operations team changes

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 5ad739f
• Storybooks Preview
• Documentation Changes

Metrics [docs]

✅ unchanged

History

• 💚 Build #128986 succeeded 1a81db3
• 💚 Build #128956 succeeded 2dc884c
• 💔 Build #128949 failed fc91354
• 💚 Build #128922 succeeded d111a12
• 💚 Build #128650 succeeded 2dcb164

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💔 Backport failed

Status	Branch	Result
❌	7.x	Commit could not be cherrypicked due to conflicts

To backport manually run:
node scripts/backport --pr 99148