…heck

* commit '6f040b29a5220ce12886a9731f656613e50aff06': (34 commits)
  [Entity Analytics] Add entity resolution UI to service flyout (elastic#260504)
  [Dashboard] Fix setState in embeddables (elastic#260082)
  [EDR Workflows] Unskip FTR tests that failed due to transient Fleet service unavailability (elastic#260519)
  [Observability:Streams] Fix query streams error handling test (elastic#260777)
  [Alerting v2] Dispatcher grouping modes, throttle strategies, and matcher autosuggestion (elastic#260249)
  [Dashboard] State extraction as a consistent override (elastic#259839)
  [Alerting v2] [Rule authoring] Fix rule name validation and error visibility in create/edit flow (elastic#260337)
  [Fix] re-introduce sln breadcrumbs to unified rules (elastic#260289)
  [Security Solution][Endpoint] Updated kibana docs to include `xpack.securitySolution.maxEndpointScriptFileSize` as configurable in cloud (elastic#260568)
  [Alerting v2] updated the alerting-v2-constants package with artifacts constants, fix to the runbook max characters (elastic#260342)
  [Automatic Import V2] Provide user tooltips (elastic#260725)
  [One Workflow] Deduplicate step types by base type in workflow list (elastic#260763)
  [Security Solution] Execution results UI: Enable the feature flag (elastic#260711)
  [Metrics][Discover] internal/search/esql_async returns 200 but METRICS_INFO responds with error (elastic#260746)
  Collapse redundant anyOf/oneOf array unions in OAS query params (elastic#260585)
  [Unified rules] Hide stack rules from global search (elastic#260088)
  [Agent Builder] Sidebar navigation updates (elastic#260728)
  [* As Code] Use PUT for upserts (elastic#260318)
  Update EUI to v114.0.0 (elastic#259497)
  [Entity Resolution] Add contextual-security-apps as co-owner of resolution paths (elastic#260659)
  ...

# Conflicts:
#	src/platform/plugins/shared/dashboard/public/index.ts

#### TL;DR:
The architecture changed from “children know how to reset themselves” to
“parents own the target serialized state and tell children exactly which
state to apply.”

## To test
Please test your embeddables by:
1. Making changes to the internals of your embeddable state (NOT grid
changes)
2. Verify "Unsaved changes" badge appears
3. refresh the page - verify the state is as expected (with unsaved
changes on)
4. "reset changes" on Dashboard
5. Verify the state has been properly reverted to the last saved state

## Summary
I changed the embeddable state model so the framework no longer treats
"reset to last saved" as the primitive operation. The primitive is now
"apply this serialized state snapshot". This fixes the bug where
dashboard-driven state updates were incorrectly using child reset
behavior and therefore restoring the last saved child state instead of
the state requested by the parent.

## What Changed

The main architectural change is that child embeddables now expose an
explicit serialized-state application capability through
`applySerializedState(state)`. Before this change, the dashboard
reset/apply flow relied on `resetUnsavedChanges()`, which only means "go
back to your own last saved baseline". That is the wrong abstraction
when the parent already has a target state and wants the child to adopt
that exact state.

Now the contract is:
- Parent serializes and owns the desired dashboard state snapshot.
- Layout manager deserializes child state from that snapshot.
- Each child that supports serialized state application receives its
exact next state through `applySerializedState(...)`.
- Dirty-state tracking remains separate from the question of what state
should be applied.

## Contract Changes
`PublishesUnsavedChanges` was simplified and now represents only:
- `serializeState()`
- `applySerializedState(...)`
- `hasUnsavedChanges$`
`resetUnsavedChanges()` was removed from the shared embeddable contract,
because it was just convenience sugar and not the real framework
primitive - so it's better not to have it, because otherwise we'll have
to keep both in sync.

## Dashboard / Container Flow

The dashboard container and layout manager were updated to use the new
capability directly.
The flow is now:
1. `dashboardApi.setState(...)` receives a full dashboard state
snapshot.
2. `layoutManager` deserializes layout and per-panel child state.
6. For each existing child, if it supports serialized-state application,
the layout manager calls `child.applySerializedState(nextChildState)`.
7. Children rehydrate themselves from the state provided by the parent.
This is the key architectural fix: the container now pushes the intended
state down, instead of asking children to infer it by resetting
themselves.

## Future improvements:

1. Make serialized-state support more explicit in the type system. Right
now PublishesUnsavedChanges implies state management capability; we
could split “dirty tracking” from “serialized state manager” even more
clearly if we want the contracts to stay very precise - but that's a
bigger effort (a lot of reviewers too!) and I am happy to work later
down the road.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>