Fix "@ts-expect-error upgrade typescript v5.1.6" in Security AET code

[semd]

https://github.com/elastic/kibana/pull/186437 upgrades upgrade typescript into v5.1.6

In order to make assumptions over the codebase and all the type of errors I choose to mark the failures with @ts-expect-error and let each team decide how to handle it. There is a list below with the files (and teams those belong to) where the annotations were added. If each team could provide help of fixing the ones under their domain it would be fantastic. It can be done in this PR or in subsequent ones.

Below are list of @ts-expect-error upgrade typescript v5.1.6 that need to be resolved once https://github.com/elastic/kibana/pull/186437 is merged

@elastic/security-solution

• [ ] x-pack/plugins/security_solution/common/api/detection_engine/rule_management/import_rules/rule_to_import.test.ts
• [ ] x-pack/plugins/security_solution/common/endpoint/generate_data.ts
• [ ] x-pack/plugins/security_solution/public/common/components/guided_onboarding_tour/tour.test.tsx
• [ ] x-pack/plugins/security_solution/public/common/components/matrix_histogram/index.tsx
• [ ] x-pack/plugins/security_solution/public/common/components/ml/links/create_explorer_link.tsx
• [x] x-pack/plugins/security_solution/public/entity_analytics/components/asset_criticality_file_uploader/reducer.test.ts
• [ ] x-pack/plugins/security_solution/public/explore/users/pages/details/breadcrumbs.ts
• [ ] x-pack/plugins/security_solution/public/management/services/exceptions_list/check_artifact_has_data.ts
• [ ] x-pack/plugins/security_solution/scripts/run_cypress/parallel.ts

@elastic/security-threat-hunting-investigations

• [x] x-pack/plugins/security_solution/common/utils/field_formatters.ts
• [x] x-pack/plugins/timelines/common/utils/field_formatters.ts
• [x] x-pack/plugins/security_solution/public/timelines/containers/index.tsx
• [x] x-pack/plugins/security_solution/server/lib/timeline/utils/compare_timelines_status.ts

### Tasks
- [ ] https://github.com/elastic/kibana/issues/188815

[elasticmachine]

Pinging @elastic/security-threat-hunting-explore (Team:Threat Hunting:Explore)

[elasticmachine]

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

[elasticmachine]

Pinging @elastic/security-entity-analytics (Team:Entity Analytics)

[jaredburgettelastic]

Looks like fixing the Entity Analytics file was already taken care of by the original PR, instead of adding @ts-expect-error. As it was a test file, and the change was just to some mocked data, no followup items needed on the part of @elastic/security-entity-analytics.

Thanks for the heads up @semd and @michaelolo24 ! I've checked off that file as done above.