Migrates index_management & runtime_fields to TS project refs

[TinaHeiligers]

Summary

Partially addresses #89321

tsc compiler performance with running node --max-old-space-size=4096 ./node_modules/.bin/tsc -p x-pack/tsconfig.json --extendedDiagnostics --noEmit

Before
Files: 15620
Lines: 1645697

After
Files: 14711
Lines: 1600254

Updated 1 Feb 2021
Note: The PR includes the changes in #89699 and, potentially, duplicates migration of runtime_fields to a TS project ref.

[TinaHeiligers]

@elasticmachine merge upstream

[mshustov]

Aren't the Before and After values reversed?

[TinaHeiligers]

@restrry The updated values now reflect that after the migration, we have fewer Files and Lines than before.

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 3f572af

Metrics [docs]

✅ unchanged

History

• 💚 Build #103083 succeeded 57ba4fa
• 💛 Build #102835 was flaky 4a13abc
• 💚 Build #102611 succeeded fdc274d
• 💚 Build #102455 succeeded 0ce0fdd
• 💚 Build #102432 succeeded c53a53d

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

[jloleysens]

These changes look good to me! Did not test compiling locally, happy that CI is passing though.

[jloleysens]

Just curious, why are these needed?

[TinaHeiligers]

The type isn't inferred from formSetup and the typescript project couldn't build.

[jloleysens]

Ah OK. It is surprising that .bind returns any! What we'd like to express is:

const a = (a: number) => {};

const b: () => ReturnType<typeof a> = a.bind(null, 1);

Not sure what else could be done, other than enabling strictBindCallApply in tsconfig, which is a breaking type check change -- but would solve this for us :)