## Summary
We are removing duplicated code in sections of plugins into the kibana/packages folder. This is phase 1 of 4+ where:
Phase 1: Lift and shift the io-ts code into `kibana/packages/kbn-securitysolution-io-ts-utils`
Phase 2: Deprecate the utils across plugins any copied code
Phase 3: Replace the deprecated types with the ones in here where we can. [Strangle pattern](https://martinfowler.com/bliki/StranglerFigApplication.html)
Phase 4+: (potentially) consolidating any duplication or everything altogether with the `kbn-io-ts-utils` project
### Checklist
- [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
* chore(NA): moving @kbn/analytics into bazel
* chore(NA): fix type check for package migration
* chore(NA): fix type check for package migration
* chore(NA): fix type check for package migration
* chore(NA): separate type generating from server code
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* chore(NA): moving @kbn/config-schema into bazel
* chore(NA): correctly format packages for the new bazel standards
* chore(NA): correctly maps srcs into source_files
* chore(NA): remove config-schema dep from legacy built packages package.jsons
* chore(NA): include kbn/config-schema in the list of bazel packages to be built
* chore(NA): change import to fix typechecking
* chore(NA): remove dependency on new package built by bazel
* chore(NA): be more explicit about incremental setting
* chore(NA): include pretty in the args for ts_project rule
* docs(NA): include package migration completion in the developer getting started
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* chore(NA): moving @kbn/apm-utils into bazel
* chore(NA): add kbn/apm-utils into package.json
* chore(NA): missing standard on build file globs
* chore(NA): be more explicit about incremental setting
* chore(NA): include pretty in the args for ts_project rule
* docs(NA): include package migration completion in the developer getting started
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* chore(NA): bazel projects support initial flag on kbn pm
* chore(NA): every needed step to build production bazel packages except the final function
* chore(NA): include build bazel production projects on kibana distributable build
* chore(NA): support bazel packages when creating the package.json
* chore(NA): including last changes on kbn pm and build distributable to support both bazel and kbn packages
* chore(NA): missing annotation on build bazel packages
* chore(NA): changed values on bazelrc common
* chore(NA): fix bazel common rc
* chore(NA): auto discovery if a kbn package is a Bazel package
* chore(NA): last details to make bazel packages to built on distributable scripts
* chore(NA): removed wrongly added line to x-pack package.json
* chore(NA): apply correct formating
* chore(NA): move into bazel bin
* chore(NA): merge chnages on kbn pm
* chore(NA): correctly setup ignore files for new bazel aggregated folder
* chore(NA): merge with last master
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
