[Milestone 1] Update latest findings indices references in Kibana

[opauloh]

Motivation

Once the latest misconfigurations dataview is created in this ticket, we need to update the references from the current latest findings indices to the new one.

Definition of done

• Latest findings DataView in cloud_security_posture/common/constants.ts points to the new dataview logs-*_latest_misconfigurations_cdr.
• The current latest transform index should keep working and should not be affected by the new changes.

Out of scope

Requirements

• https://github.com/elastic/security-team/issues/12314

Related tasks/epics

• [Milestone 1] Create latest misconfigurations CDR dataview per space #187433

[elasticmachine]

Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security)

[opauloh]

This ticket overlaps with #179628 as this change is also contemplated by CDR, this ticket can be closed if #179628 is completed.

[CohenIdo]

Upcoming Change: Impact and Required Validation

The upcoming update, which replaces the reference to the latest index, may potentially impact various features and workflows across our product.
While I have taken every effort to ensure a seamless transition, it is important that we thoroughly review each component to confirm it continues to function correctly across different use cases.

Tlle latest findings index occurrences replaced with an index alias.
The alias used is the same one that will be introduced in the upcoming integration version: security_solution-cloud_security_posture.misconfiguration_latest.

For integration versions earlier than 2.00, we will manually create an index alias for the deprecated latest index logs-cloud_security_posture.findings_latest-default.
For integration versions 2.00 and above, the index alias will be automatically created or updated as part of the Transform setup.

This approach ensures we always reference the correct index using a consistent alias, depending on the Kibana and Integration state. See the table below for details:

Scenario	Behavior
Existing users upgrading their Kibana cluster	A new index alias will be created, replacing references to the latest findings index. On subsequent upgrades, the alias will automatically point to the correct index behind the scenes.
New users (no integration installed) upgrading Kibana	The index alias will not be installed during the Kibana upgrade. It will be added later when the integration is installed as part of its assets.
Serverless users installing the integration after the Kibana change but before the integration update	The index alias will point to the old latest findings index.

Dependency Versions to Test:

• Integration version < 2.00 with a fresh installation
• Integration version < 2.00 with an existing installation (including integration upgrade and Kibana upgrade):
• Integration version ≥ 2.00 with a fresh installation

Upgrade Test Step by Step

1. Install the CSPM integration with a version earlier than 2.00.
2. Index some findings, then verify that the latest index is populated and that data appears on both the Findings and Dashboard pages.
3. Go to the Integrations page and enable the Display beta integrations toggle.
4. Navigate to the Cloud Security Posture integration, go to Settings, and upgrade to the latest version.
5. Confirm that the new index security_solution-cloud_security_posture.misconfiguration_latest is populated (wait for the transform’s first cycle to complete).
6. Delete the data from the logs-cloud_security_posture.findings_latest-default index.
7. Open the Findings page.
8. Check the score index and verify that new entries have been indexed..

Key Areas to Validate:

• Integration installation process
• Findings page
• Dashboard page
• Benchmark rules page
• Score task
• Status API
• Alerts
• Metering task
• Telemetry