> [!IMPORTANT]
> Because of the size of this feature, maintaining this PR is extremely
time intensive. It would be appreciated if reviews could be done ASAP in
order to reduce the effort involved in constantly handling conflicts
:bow:

Closes elastic#154749
Closes elastic#210620
Closes elastic#230633

## Summary

This PR adds controls as a panel type - allowing users to freely place
controls anywhere in their dashboards. In order to get the desired
behaviour, we have removed the `controlGroup` embeddable in favour of
making each control type an individual embeddable - this allows a single
panel to contain a single control rather than an entire control group.

This behaviour is especially useful for ES|QL variable controls, since
you can now place your controls beside the ES|QL panels that they
control. To make this more obvious, we added a new `beside` parameter to
the `addNewPanel` options - that way, when adding a new control via the
ES|QL panel editor, it will be added **beside** the relevant panel:


https://github.com/user-attachments/assets/360bbd4c-83f2-467f-98aa-29ff27228b29


> [!NOTE]
> Notice that the new control is not currently focused. This will be
addressed in a [follow
up](elastic#236021).

## Notable Changes

### Filter Scoping

When dragged into a section, control panels will only target the panels
**in that section** - this allows users to target a specific subset of
panels with controls. If a control panel does not belong to a
collapsible section (or if it is pinned to the top of the dashboard), it
is considered to have "global" scope and will impact **all other
panels** on the Dashboard.

In order to get this behaviour to function, we added two pieces of meta
data to the output filters:
1. `group` - this is used the specify which collapsible section (if any)
that control belongs to. This makes it so that the filters output by a
control only target panels in the shared section; however, if the
control does not belong to a section, then it is treated as "global" and
impacts every panel in the dashboard.
2. `controlledBy` - this is used to specify the control ID that is
responsible for generating the filter. This makes it so that controls
are not filtered by their **own filters** - they simply ignore filters
with a `controlledBy` ID that matches their own.


https://github.com/user-attachments/assets/b1b0dd63-e785-45cd-bc13-5f46c98867af

### Chaining System

We removed the controls "chaining system" - instead, controls are always
universally chained. In order to replicate old behaviour of **no**
chaining, users can turn off the `useGlobalFilters` setting for each
individual control - and to make this transition easier, we have added a
migration where all control groups that had `chainingSystem === 'NONE'`
will have `useGlobalFilters` turned off for all controls.


https://github.com/elastic/kibana/blob/8fdcf1e73af25a26f8792db686c3f4f33e203d0b/src/platform/plugins/shared/dashboard/public/dashboard_app/url/bwc/extract_control_group_state.ts#L101-L108


https://github.com/elastic/kibana/blob/8fdcf1e73af25a26f8792db686c3f4f33e203d0b/src/platform/plugins/shared/dashboard/server/api/transforms/out/transform_control_group_out.ts#L32-L38


### Pinned controls

The old "control group" is now referred to as **pinned controls** - i.e.
control panels that belong in the sticky header of Dashboard - and they
are rendered via the new `RenderControls` React component. They should
look and function like the old control group - with the only exception
being that **universal chaining** is now the default. Control panels can
be pinned and unpinned via a new action in order to take them in and out
of the sticky header:



https://github.com/user-attachments/assets/b70a717d-2f35-4e5e-89b5-f88fabf58b1e

Note that, if you add a control directly from the "Controls" sub menu,
it will be added as a pinned control - this is also the only place to
add a timeslider control, since it does not make sense as an individual
panel type. If you add a control via the "Add panel" flyout, on the
other hand, it will be added as a normal, unpinned panel.


### Auto apply filters

Because controls are now individual embeddables (and therefore each
control panel only has a single control), the old apply button no longer
made sense - instead, if you go to Dashboard settings and turn off "Auto
apply filters" (which used to be a control group level setting), the
publishing of filters is now controlled by the unified search "Apply"
button:



https://github.com/user-attachments/assets/02159d6d-6f79-4418-892f-069c145d1ddb



## Notes for Reviewers
- Checkout
elastic#245588 (comment) to
be redirected to my first code comment.
- We added more options to the `addNewPanel` function for embeddables,
which meant that a single boolean for `displaySuccessMessage` was no
longer enough. So, you will see quite a few changes like this in this
PR:

  ```
    embeddable.addNewPanel(
      ...
      {
        displaySuccessMessage: true,
      }
    );
  ```
  
All of these are just to keep behaviour consistent after adding these
new options.

- In order to make testing BWC easier, I have compiled a few different
URLs:
  <details>
<summary><b>8.15</b> - Logs Dashboard with Control Selections</summary>
  
   `

&_a=(controlGroupInput:(chainingSystem:HIERARCHICAL,controlStyle:oneLine,id:control_group_65362d09-fc37-40d4-92bf-cda8e572996b,ignoreParentSettings:(ignoreFilters:!f,ignoreQuery:!f,ignoreTimerange:!f,ignoreValidations:!f),panels:('612f8db8-9ba9-41cf-a809-d133fe9b83a8':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:geo.src,id:'612f8db8-9ba9-41cf-a809-d133fe9b83a8',title:'Source%20Country'),grow:!t,order:0,type:optionsListControl,width:small),'6bf7a1b4-282e-43ac-aa46-81b97fa3acae':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:bytes,id:'6bf7a1b4-282e-43ac-aa46-81b97fa3acae',title:Bytes),grow:!t,order:2,type:rangeSliderControl,width:small),'9807212f-5078-4c42-879c-6f28b3033fc9':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:machine.os.keyword,id:'9807212f-5078-4c42-879c-6f28b3033fc9',parentFieldName:machine.os,selectedOptions:!('win%207',osx),title:OS),grow:!t,order:1,type:optionsListControl,width:small)),showApplySelections:!t))
    `
  </details>
  
  
  <details>
<summary><b>8.15</b> - Logs Dashboard with
<code>showApplySelection</code> on</summary>
  
   `
    &_a=(controlGroupInput:(showApplySelections:!t))
    `
  </details>
  
  <details>
<summary><b>8.15</b> - Logs Dashboard with <code>chainingSystem =
'NONE'</code></summary>
  
   `

&_a=(controlGroupInput:(chainingSystem:NONE,controlStyle:oneLine,id:control_group_65362d09-fc37-40d4-92bf-cda8e572996b,ignoreParentSettings:(ignoreFilters:!f,ignoreQuery:!f,ignoreTimerange:!f,ignoreValidations:!f),panels:('612f8db8-9ba9-41cf-a809-d133fe9b83a8':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:geo.src,id:'612f8db8-9ba9-41cf-a809-d133fe9b83a8',title:'Source%20Country'),grow:!t,order:0,type:optionsListControl,width:small),'6bf7a1b4-282e-43ac-aa46-81b97fa3acae':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:bytes,id:'6bf7a1b4-282e-43ac-aa46-81b97fa3acae',title:Bytes),grow:!t,order:2,type:rangeSliderControl,width:small),'9807212f-5078-4c42-879c-6f28b3033fc9':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:machine.os.keyword,id:'9807212f-5078-4c42-879c-6f28b3033fc9',parentFieldName:machine.os,title:OS),grow:!t,order:1,type:optionsListControl,width:small)),showApplySelections:!f))
    `
  </details>
  
  
  <details>
<summary><b>8.18</b> - Logs Dashboard with Control Selections</summary>
  
   `

&_a=(controlGroupState:(initialChildControlState:(%27612f8db8-9ba9-41cf-a809-d133fe9b83a8%27:(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,exclude:!f,existsSelected:!n,fieldName:geo.src,grow:!t,hideActionBar:!n,hideExclude:!n,hideExists:!n,hideSort:!n,order:0,placeholder:!n,runPastTimeout:!n,searchTechnique:prefix,selectedOptions:!(US),singleSelect:!n,sort:(by:_count,direction:desc),title:%27Source%20Country%27,type:optionsListControl,width:small),%276bf7a1b4-282e-43ac-aa46-81b97fa3acae%27:(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,fieldName:bytes,grow:!t,order:2,step:1,title:Bytes,type:rangeSliderControl,value:!(%276255%27,%2715901%27),width:small),%279807212f-5078-4c42-879c-6f28b3033fc9%27:(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,exclude:!n,existsSelected:!n,fieldName:machine.os.keyword,grow:!t,hideActionBar:!n,hideExclude:!n,hideExists:!n,hideSort:!n,order:1,placeholder:!n,runPastTimeout:!n,searchTechnique:prefix,selectedOptions:!(%27win%20xp%27,%27win%208%27),singleSelect:!n,sort:(by:_count,direction:desc),title:OS,type:optionsListControl,width:small))))
    `
  </details>
  
  
  <details>
<summary><b>8.18</b> - Logs Dashboard with
<code>autoApplySelections</code> off</summary>
  
   `
    &_a=(controlGroupState:(autoApplySelections:!f))
    `
  </details>
  
  
  
  <details>
<summary><b>8.18</b> - Logs Dashboard with <code>chainingSystem =
'NONE'</code></summary>
  
   `

&_a=(controlGroupState:(chainingSystem:NONE,initialChildControlState:('612f8db8-9ba9-41cf-a809-d133fe9b83a8':(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,exclude:!f,existsSelected:!n,fieldName:geo.src,grow:!t,hideActionBar:!n,hideExclude:!n,hideExists:!n,hideSort:!n,order:0,placeholder:!n,runPastTimeout:!n,searchTechnique:prefix,singleSelect:!n,sort:(by:_count,direction:desc),title:'Source%20Country',type:optionsListControl,width:small),'6bf7a1b4-282e-43ac-aa46-81b97fa3acae':(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,fieldName:bytes,grow:!t,order:2,step:1,title:Bytes,type:rangeSliderControl,value:!n,width:small),'9807212f-5078-4c42-879c-6f28b3033fc9':(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,exclude:!n,existsSelected:!n,fieldName:machine.os.keyword,grow:!t,hideActionBar:!n,hideExclude:!n,hideExists:!n,hideSort:!n,order:1,placeholder:!n,runPastTimeout:!n,searchTechnique:prefix,selectedOptions:!(),singleSelect:!n,sort:(by:_count,direction:desc),title:OS,type:optionsListControl,width:small))))
    `
  </details>
  
  <details>
<summary><b>9.2</b> - Logs Dashboard with Control Selections</summary>
  
   `

&_a=(controlGroupInput:(autoApplySelections:!t,chainingSystem:HIERARCHICAL,controls:!((controlConfig:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',exclude:!f,existsSelected:!f,fieldName:geo.src,searchTechnique:prefix,selectedOptions:!(US),sort:(by:_count,direction:desc),title:'Source%20Country'),grow:!t,id:'612f8db8-9ba9-41cf-a809-d133fe9b83a8',order:0,type:optionsListControl,width:small),(controlConfig:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',exclude:!f,existsSelected:!f,fieldName:machine.os.keyword,searchTechnique:prefix,selectedOptions:!(osx,'win%207','win%208',ios),sort:(by:_count,direction:desc),title:OS),grow:!t,id:'9807212f-5078-4c42-879c-6f28b3033fc9',order:1,type:optionsListControl,width:small),(controlConfig:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',fieldName:bytes,step:1,title:Bytes,value:!('6696','14567')),grow:!t,id:'6bf7a1b4-282e-43ac-aa46-81b97fa3acae',order:2,type:rangeSliderControl,width:small)),ignoreParentSettings:(ignoreFilters:!f,ignoreQuery:!f,ignoreTimerange:!f,ignoreValidations:!f),labelPosition:oneLine),references:!((id:'90943e30-9a47-11e8-b64d-95841ca0b247',name:'controlGroup_612f8db8-9ba9-41cf-a809-d133fe9b83a8:optionsListDataView',type:index-pattern),(id:'90943e30-9a47-11e8-b64d-95841ca0b247',name:'controlGroup_9807212f-5078-4c42-879c-6f28b3033fc9:optionsListDataView',type:index-pattern),(id:'90943e30-9a47-11e8-b64d-95841ca0b247',name:'controlGroup_6bf7a1b4-282e-43ac-aa46-81b97fa3acae:rangeSliderDataView',type:index-pattern)),viewMode:edit)
    `
  </details>

### Checklist

- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [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
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/10172
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/10186
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

## Release note

Controls are now available as a panel type, which means that they can be
freely placed anywhere in your Dashboards! The output filters are
limited to their sections, which allows you to target only a subset of
panels with a given control. If desired, controls can still be pinned to
the top of the Dashboard with a global scope.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Zac Xeper <Zacqary@users.noreply.github.com>
Co-authored-by: Catherine Liu <catherine.liu@elastic.co>
Co-authored-by: Zacqary Xeper <zacqary.xeper@elastic.co>
Co-authored-by: Stratou <efstratia.kalafateli@elastic.co>
Co-authored-by: Davis McPhee <davis.mcphee@elastic.co>

## Summary

When resolving merge conflicts with
#245310 in the [Controls Anywhere
PR](#245588), we accidentally
ended up with control references being spread twice. This PR undoes
that.

> [!IMPORTANT]
> Because of the size of this feature, maintaining this PR is extremely
time intensive. It would be appreciated if reviews could be done ASAP in
order to reduce the effort involved in constantly handling conflicts
:bow:

Closes elastic#154749
Closes elastic#210620
Closes elastic#230633

This PR adds controls as a panel type - allowing users to freely place
controls anywhere in their dashboards. In order to get the desired
behaviour, we have removed the `controlGroup` embeddable in favour of
making each control type an individual embeddable - this allows a single
panel to contain a single control rather than an entire control group.

This behaviour is especially useful for ES|QL variable controls, since
you can now place your controls beside the ES|QL panels that they
control. To make this more obvious, we added a new `beside` parameter to
the `addNewPanel` options - that way, when adding a new control via the
ES|QL panel editor, it will be added **beside** the relevant panel:

https://github.com/user-attachments/assets/360bbd4c-83f2-467f-98aa-29ff27228b29

> [!NOTE]
> Notice that the new control is not currently focused. This will be
addressed in a [follow
up](elastic#236021).

When dragged into a section, control panels will only target the panels
**in that section** - this allows users to target a specific subset of
panels with controls. If a control panel does not belong to a
collapsible section (or if it is pinned to the top of the dashboard), it
is considered to have "global" scope and will impact **all other
panels** on the Dashboard.

In order to get this behaviour to function, we added two pieces of meta
data to the output filters:
1. `group` - this is used the specify which collapsible section (if any)
that control belongs to. This makes it so that the filters output by a
control only target panels in the shared section; however, if the
control does not belong to a section, then it is treated as "global" and
impacts every panel in the dashboard.
2. `controlledBy` - this is used to specify the control ID that is
responsible for generating the filter. This makes it so that controls
are not filtered by their **own filters** - they simply ignore filters
with a `controlledBy` ID that matches their own.

https://github.com/user-attachments/assets/b1b0dd63-e785-45cd-bc13-5f46c98867af

We removed the controls "chaining system" - instead, controls are always
universally chained. In order to replicate old behaviour of **no**
chaining, users can turn off the `useGlobalFilters` setting for each
individual control - and to make this transition easier, we have added a
migration where all control groups that had `chainingSystem === 'NONE'`
will have `useGlobalFilters` turned off for all controls.

https://github.com/elastic/kibana/blob/8fdcf1e73af25a26f8792db686c3f4f33e203d0b/src/platform/plugins/shared/dashboard/public/dashboard_app/url/bwc/extract_control_group_state.ts#L101-L108

https://github.com/elastic/kibana/blob/8fdcf1e73af25a26f8792db686c3f4f33e203d0b/src/platform/plugins/shared/dashboard/server/api/transforms/out/transform_control_group_out.ts#L32-L38

The old "control group" is now referred to as **pinned controls** - i.e.
control panels that belong in the sticky header of Dashboard - and they
are rendered via the new `RenderControls` React component. They should
look and function like the old control group - with the only exception
being that **universal chaining** is now the default. Control panels can
be pinned and unpinned via a new action in order to take them in and out
of the sticky header:

https://github.com/user-attachments/assets/b70a717d-2f35-4e5e-89b5-f88fabf58b1e

Note that, if you add a control directly from the "Controls" sub menu,
it will be added as a pinned control - this is also the only place to
add a timeslider control, since it does not make sense as an individual
panel type. If you add a control via the "Add panel" flyout, on the
other hand, it will be added as a normal, unpinned panel.

Because controls are now individual embeddables (and therefore each
control panel only has a single control), the old apply button no longer
made sense - instead, if you go to Dashboard settings and turn off "Auto
apply filters" (which used to be a control group level setting), the
publishing of filters is now controlled by the unified search "Apply"
button:

https://github.com/user-attachments/assets/02159d6d-6f79-4418-892f-069c145d1ddb

- Checkout
elastic#245588 (comment) to
be redirected to my first code comment.
- We added more options to the `addNewPanel` function for embeddables,
which meant that a single boolean for `displaySuccessMessage` was no
longer enough. So, you will see quite a few changes like this in this
PR:

  ```
    embeddable.addNewPanel(
      ...
      {
        displaySuccessMessage: true,
      }
    );
  ```

All of these are just to keep behaviour consistent after adding these
new options.

- In order to make testing BWC easier, I have compiled a few different
URLs:
  <details>
<summary><b>8.15</b> - Logs Dashboard with Control Selections</summary>

   `

&_a=(controlGroupInput:(chainingSystem:HIERARCHICAL,controlStyle:oneLine,id:control_group_65362d09-fc37-40d4-92bf-cda8e572996b,ignoreParentSettings:(ignoreFilters:!f,ignoreQuery:!f,ignoreTimerange:!f,ignoreValidations:!f),panels:('612f8db8-9ba9-41cf-a809-d133fe9b83a8':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:geo.src,id:'612f8db8-9ba9-41cf-a809-d133fe9b83a8',title:'Source%20Country'),grow:!t,order:0,type:optionsListControl,width:small),'6bf7a1b4-282e-43ac-aa46-81b97fa3acae':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:bytes,id:'6bf7a1b4-282e-43ac-aa46-81b97fa3acae',title:Bytes),grow:!t,order:2,type:rangeSliderControl,width:small),'9807212f-5078-4c42-879c-6f28b3033fc9':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:machine.os.keyword,id:'9807212f-5078-4c42-879c-6f28b3033fc9',parentFieldName:machine.os,selectedOptions:!('win%207',osx),title:OS),grow:!t,order:1,type:optionsListControl,width:small)),showApplySelections:!t))
    `
  </details>

  <details>
<summary><b>8.15</b> - Logs Dashboard with
<code>showApplySelection</code> on</summary>

   `
    &_a=(controlGroupInput:(showApplySelections:!t))
    `
  </details>

  <details>
<summary><b>8.15</b> - Logs Dashboard with <code>chainingSystem =
'NONE'</code></summary>

   `

&_a=(controlGroupInput:(chainingSystem:NONE,controlStyle:oneLine,id:control_group_65362d09-fc37-40d4-92bf-cda8e572996b,ignoreParentSettings:(ignoreFilters:!f,ignoreQuery:!f,ignoreTimerange:!f,ignoreValidations:!f),panels:('612f8db8-9ba9-41cf-a809-d133fe9b83a8':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:geo.src,id:'612f8db8-9ba9-41cf-a809-d133fe9b83a8',title:'Source%20Country'),grow:!t,order:0,type:optionsListControl,width:small),'6bf7a1b4-282e-43ac-aa46-81b97fa3acae':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:bytes,id:'6bf7a1b4-282e-43ac-aa46-81b97fa3acae',title:Bytes),grow:!t,order:2,type:rangeSliderControl,width:small),'9807212f-5078-4c42-879c-6f28b3033fc9':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:machine.os.keyword,id:'9807212f-5078-4c42-879c-6f28b3033fc9',parentFieldName:machine.os,title:OS),grow:!t,order:1,type:optionsListControl,width:small)),showApplySelections:!f))
    `
  </details>

  <details>
<summary><b>8.18</b> - Logs Dashboard with Control Selections</summary>

   `

&_a=(controlGroupState:(initialChildControlState:(%27612f8db8-9ba9-41cf-a809-d133fe9b83a8%27:(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,exclude:!f,existsSelected:!n,fieldName:geo.src,grow:!t,hideActionBar:!n,hideExclude:!n,hideExists:!n,hideSort:!n,order:0,placeholder:!n,runPastTimeout:!n,searchTechnique:prefix,selectedOptions:!(US),singleSelect:!n,sort:(by:_count,direction:desc),title:%27Source%20Country%27,type:optionsListControl,width:small),%276bf7a1b4-282e-43ac-aa46-81b97fa3acae%27:(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,fieldName:bytes,grow:!t,order:2,step:1,title:Bytes,type:rangeSliderControl,value:!(%276255%27,%2715901%27),width:small),%279807212f-5078-4c42-879c-6f28b3033fc9%27:(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,exclude:!n,existsSelected:!n,fieldName:machine.os.keyword,grow:!t,hideActionBar:!n,hideExclude:!n,hideExists:!n,hideSort:!n,order:1,placeholder:!n,runPastTimeout:!n,searchTechnique:prefix,selectedOptions:!(%27win%20xp%27,%27win%208%27),singleSelect:!n,sort:(by:_count,direction:desc),title:OS,type:optionsListControl,width:small))))
    `
  </details>

  <details>
<summary><b>8.18</b> - Logs Dashboard with
<code>autoApplySelections</code> off</summary>

   `
    &_a=(controlGroupState:(autoApplySelections:!f))
    `
  </details>

  <details>
<summary><b>8.18</b> - Logs Dashboard with <code>chainingSystem =
'NONE'</code></summary>

   `

&_a=(controlGroupState:(chainingSystem:NONE,initialChildControlState:('612f8db8-9ba9-41cf-a809-d133fe9b83a8':(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,exclude:!f,existsSelected:!n,fieldName:geo.src,grow:!t,hideActionBar:!n,hideExclude:!n,hideExists:!n,hideSort:!n,order:0,placeholder:!n,runPastTimeout:!n,searchTechnique:prefix,singleSelect:!n,sort:(by:_count,direction:desc),title:'Source%20Country',type:optionsListControl,width:small),'6bf7a1b4-282e-43ac-aa46-81b97fa3acae':(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,fieldName:bytes,grow:!t,order:2,step:1,title:Bytes,type:rangeSliderControl,value:!n,width:small),'9807212f-5078-4c42-879c-6f28b3033fc9':(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,exclude:!n,existsSelected:!n,fieldName:machine.os.keyword,grow:!t,hideActionBar:!n,hideExclude:!n,hideExists:!n,hideSort:!n,order:1,placeholder:!n,runPastTimeout:!n,searchTechnique:prefix,selectedOptions:!(),singleSelect:!n,sort:(by:_count,direction:desc),title:OS,type:optionsListControl,width:small))))
    `
  </details>

  <details>
<summary><b>9.2</b> - Logs Dashboard with Control Selections</summary>

   `

&_a=(controlGroupInput:(autoApplySelections:!t,chainingSystem:HIERARCHICAL,controls:!((controlConfig:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',exclude:!f,existsSelected:!f,fieldName:geo.src,searchTechnique:prefix,selectedOptions:!(US),sort:(by:_count,direction:desc),title:'Source%20Country'),grow:!t,id:'612f8db8-9ba9-41cf-a809-d133fe9b83a8',order:0,type:optionsListControl,width:small),(controlConfig:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',exclude:!f,existsSelected:!f,fieldName:machine.os.keyword,searchTechnique:prefix,selectedOptions:!(osx,'win%207','win%208',ios),sort:(by:_count,direction:desc),title:OS),grow:!t,id:'9807212f-5078-4c42-879c-6f28b3033fc9',order:1,type:optionsListControl,width:small),(controlConfig:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',fieldName:bytes,step:1,title:Bytes,value:!('6696','14567')),grow:!t,id:'6bf7a1b4-282e-43ac-aa46-81b97fa3acae',order:2,type:rangeSliderControl,width:small)),ignoreParentSettings:(ignoreFilters:!f,ignoreQuery:!f,ignoreTimerange:!f,ignoreValidations:!f),labelPosition:oneLine),references:!((id:'90943e30-9a47-11e8-b64d-95841ca0b247',name:'controlGroup_612f8db8-9ba9-41cf-a809-d133fe9b83a8:optionsListDataView',type:index-pattern),(id:'90943e30-9a47-11e8-b64d-95841ca0b247',name:'controlGroup_9807212f-5078-4c42-879c-6f28b3033fc9:optionsListDataView',type:index-pattern),(id:'90943e30-9a47-11e8-b64d-95841ca0b247',name:'controlGroup_6bf7a1b4-282e-43ac-aa46-81b97fa3acae:rangeSliderDataView',type:index-pattern)),viewMode:edit)
    `
  </details>

- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [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
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/10172
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/10186
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

Controls are now available as a panel type, which means that they can be
freely placed anywhere in your Dashboards! The output filters are
limited to their sections, which allows you to target only a subset of
panels with a given control. If desired, controls can still be pinned to
the top of the Dashboard with a global scope.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Zac Xeper <Zacqary@users.noreply.github.com>
Co-authored-by: Catherine Liu <catherine.liu@elastic.co>
Co-authored-by: Zacqary Xeper <zacqary.xeper@elastic.co>
Co-authored-by: Stratou <efstratia.kalafateli@elastic.co>
Co-authored-by: Davis McPhee <davis.mcphee@elastic.co>

## Summary

When resolving merge conflicts with
elastic#245310 in the [Controls Anywhere
PR](elastic#245588), we accidentally
ended up with control references being spread twice. This PR undoes
that.

> [!IMPORTANT]
> Because of the size of this feature, maintaining this PR is extremely
time intensive. It would be appreciated if reviews could be done ASAP in
order to reduce the effort involved in constantly handling conflicts
:bow:

Closes elastic#154749
Closes elastic#210620
Closes elastic#230633

## Summary

This PR adds controls as a panel type - allowing users to freely place
controls anywhere in their dashboards. In order to get the desired
behaviour, we have removed the `controlGroup` embeddable in favour of
making each control type an individual embeddable - this allows a single
panel to contain a single control rather than an entire control group.

This behaviour is especially useful for ES|QL variable controls, since
you can now place your controls beside the ES|QL panels that they
control. To make this more obvious, we added a new `beside` parameter to
the `addNewPanel` options - that way, when adding a new control via the
ES|QL panel editor, it will be added **beside** the relevant panel:


https://github.com/user-attachments/assets/360bbd4c-83f2-467f-98aa-29ff27228b29


> [!NOTE]
> Notice that the new control is not currently focused. This will be
addressed in a [follow
up](elastic#236021).

## Notable Changes

### Filter Scoping

When dragged into a section, control panels will only target the panels
**in that section** - this allows users to target a specific subset of
panels with controls. If a control panel does not belong to a
collapsible section (or if it is pinned to the top of the dashboard), it
is considered to have "global" scope and will impact **all other
panels** on the Dashboard.

In order to get this behaviour to function, we added two pieces of meta
data to the output filters:
1. `group` - this is used the specify which collapsible section (if any)
that control belongs to. This makes it so that the filters output by a
control only target panels in the shared section; however, if the
control does not belong to a section, then it is treated as "global" and
impacts every panel in the dashboard.
2. `controlledBy` - this is used to specify the control ID that is
responsible for generating the filter. This makes it so that controls
are not filtered by their **own filters** - they simply ignore filters
with a `controlledBy` ID that matches their own.


https://github.com/user-attachments/assets/b1b0dd63-e785-45cd-bc13-5f46c98867af

### Chaining System

We removed the controls "chaining system" - instead, controls are always
universally chained. In order to replicate old behaviour of **no**
chaining, users can turn off the `useGlobalFilters` setting for each
individual control - and to make this transition easier, we have added a
migration where all control groups that had `chainingSystem === 'NONE'`
will have `useGlobalFilters` turned off for all controls.


https://github.com/elastic/kibana/blob/8fdcf1e73af25a26f8792db686c3f4f33e203d0b/src/platform/plugins/shared/dashboard/public/dashboard_app/url/bwc/extract_control_group_state.ts#L101-L108


https://github.com/elastic/kibana/blob/8fdcf1e73af25a26f8792db686c3f4f33e203d0b/src/platform/plugins/shared/dashboard/server/api/transforms/out/transform_control_group_out.ts#L32-L38


### Pinned controls

The old "control group" is now referred to as **pinned controls** - i.e.
control panels that belong in the sticky header of Dashboard - and they
are rendered via the new `RenderControls` React component. They should
look and function like the old control group - with the only exception
being that **universal chaining** is now the default. Control panels can
be pinned and unpinned via a new action in order to take them in and out
of the sticky header:



https://github.com/user-attachments/assets/b70a717d-2f35-4e5e-89b5-f88fabf58b1e

Note that, if you add a control directly from the "Controls" sub menu,
it will be added as a pinned control - this is also the only place to
add a timeslider control, since it does not make sense as an individual
panel type. If you add a control via the "Add panel" flyout, on the
other hand, it will be added as a normal, unpinned panel.


### Auto apply filters

Because controls are now individual embeddables (and therefore each
control panel only has a single control), the old apply button no longer
made sense - instead, if you go to Dashboard settings and turn off "Auto
apply filters" (which used to be a control group level setting), the
publishing of filters is now controlled by the unified search "Apply"
button:



https://github.com/user-attachments/assets/02159d6d-6f79-4418-892f-069c145d1ddb



## Notes for Reviewers
- Checkout
elastic#245588 (comment) to
be redirected to my first code comment.
- We added more options to the `addNewPanel` function for embeddables,
which meant that a single boolean for `displaySuccessMessage` was no
longer enough. So, you will see quite a few changes like this in this
PR:

  ```
    embeddable.addNewPanel(
      ...
      {
        displaySuccessMessage: true,
      }
    );
  ```
  
All of these are just to keep behaviour consistent after adding these
new options.

- In order to make testing BWC easier, I have compiled a few different
URLs:
  <details>
<summary><b>8.15</b> - Logs Dashboard with Control Selections</summary>
  
   `

&_a=(controlGroupInput:(chainingSystem:HIERARCHICAL,controlStyle:oneLine,id:control_group_65362d09-fc37-40d4-92bf-cda8e572996b,ignoreParentSettings:(ignoreFilters:!f,ignoreQuery:!f,ignoreTimerange:!f,ignoreValidations:!f),panels:('612f8db8-9ba9-41cf-a809-d133fe9b83a8':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:geo.src,id:'612f8db8-9ba9-41cf-a809-d133fe9b83a8',title:'Source%20Country'),grow:!t,order:0,type:optionsListControl,width:small),'6bf7a1b4-282e-43ac-aa46-81b97fa3acae':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:bytes,id:'6bf7a1b4-282e-43ac-aa46-81b97fa3acae',title:Bytes),grow:!t,order:2,type:rangeSliderControl,width:small),'9807212f-5078-4c42-879c-6f28b3033fc9':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:machine.os.keyword,id:'9807212f-5078-4c42-879c-6f28b3033fc9',parentFieldName:machine.os,selectedOptions:!('win%207',osx),title:OS),grow:!t,order:1,type:optionsListControl,width:small)),showApplySelections:!t))
    `
  </details>
  
  
  <details>
<summary><b>8.15</b> - Logs Dashboard with
<code>showApplySelection</code> on</summary>
  
   `
    &_a=(controlGroupInput:(showApplySelections:!t))
    `
  </details>
  
  <details>
<summary><b>8.15</b> - Logs Dashboard with <code>chainingSystem =
'NONE'</code></summary>
  
   `

&_a=(controlGroupInput:(chainingSystem:NONE,controlStyle:oneLine,id:control_group_65362d09-fc37-40d4-92bf-cda8e572996b,ignoreParentSettings:(ignoreFilters:!f,ignoreQuery:!f,ignoreTimerange:!f,ignoreValidations:!f),panels:('612f8db8-9ba9-41cf-a809-d133fe9b83a8':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:geo.src,id:'612f8db8-9ba9-41cf-a809-d133fe9b83a8',title:'Source%20Country'),grow:!t,order:0,type:optionsListControl,width:small),'6bf7a1b4-282e-43ac-aa46-81b97fa3acae':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:bytes,id:'6bf7a1b4-282e-43ac-aa46-81b97fa3acae',title:Bytes),grow:!t,order:2,type:rangeSliderControl,width:small),'9807212f-5078-4c42-879c-6f28b3033fc9':(explicitInput:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',enhancements:(),fieldName:machine.os.keyword,id:'9807212f-5078-4c42-879c-6f28b3033fc9',parentFieldName:machine.os,title:OS),grow:!t,order:1,type:optionsListControl,width:small)),showApplySelections:!f))
    `
  </details>
  
  
  <details>
<summary><b>8.18</b> - Logs Dashboard with Control Selections</summary>
  
   `

&_a=(controlGroupState:(initialChildControlState:(%27612f8db8-9ba9-41cf-a809-d133fe9b83a8%27:(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,exclude:!f,existsSelected:!n,fieldName:geo.src,grow:!t,hideActionBar:!n,hideExclude:!n,hideExists:!n,hideSort:!n,order:0,placeholder:!n,runPastTimeout:!n,searchTechnique:prefix,selectedOptions:!(US),singleSelect:!n,sort:(by:_count,direction:desc),title:%27Source%20Country%27,type:optionsListControl,width:small),%276bf7a1b4-282e-43ac-aa46-81b97fa3acae%27:(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,fieldName:bytes,grow:!t,order:2,step:1,title:Bytes,type:rangeSliderControl,value:!(%276255%27,%2715901%27),width:small),%279807212f-5078-4c42-879c-6f28b3033fc9%27:(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,exclude:!n,existsSelected:!n,fieldName:machine.os.keyword,grow:!t,hideActionBar:!n,hideExclude:!n,hideExists:!n,hideSort:!n,order:1,placeholder:!n,runPastTimeout:!n,searchTechnique:prefix,selectedOptions:!(%27win%20xp%27,%27win%208%27),singleSelect:!n,sort:(by:_count,direction:desc),title:OS,type:optionsListControl,width:small))))
    `
  </details>
  
  
  <details>
<summary><b>8.18</b> - Logs Dashboard with
<code>autoApplySelections</code> off</summary>
  
   `
    &_a=(controlGroupState:(autoApplySelections:!f))
    `
  </details>
  
  
  
  <details>
<summary><b>8.18</b> - Logs Dashboard with <code>chainingSystem =
'NONE'</code></summary>
  
   `

&_a=(controlGroupState:(chainingSystem:NONE,initialChildControlState:('612f8db8-9ba9-41cf-a809-d133fe9b83a8':(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,exclude:!f,existsSelected:!n,fieldName:geo.src,grow:!t,hideActionBar:!n,hideExclude:!n,hideExists:!n,hideSort:!n,order:0,placeholder:!n,runPastTimeout:!n,searchTechnique:prefix,singleSelect:!n,sort:(by:_count,direction:desc),title:'Source%20Country',type:optionsListControl,width:small),'6bf7a1b4-282e-43ac-aa46-81b97fa3acae':(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,fieldName:bytes,grow:!t,order:2,step:1,title:Bytes,type:rangeSliderControl,value:!n,width:small),'9807212f-5078-4c42-879c-6f28b3033fc9':(dataViewId:%2790943e30-9a47-11e8-b64d-95841ca0b247%27,exclude:!n,existsSelected:!n,fieldName:machine.os.keyword,grow:!t,hideActionBar:!n,hideExclude:!n,hideExists:!n,hideSort:!n,order:1,placeholder:!n,runPastTimeout:!n,searchTechnique:prefix,selectedOptions:!(),singleSelect:!n,sort:(by:_count,direction:desc),title:OS,type:optionsListControl,width:small))))
    `
  </details>
  
  <details>
<summary><b>9.2</b> - Logs Dashboard with Control Selections</summary>
  
   `

&_a=(controlGroupInput:(autoApplySelections:!t,chainingSystem:HIERARCHICAL,controls:!((controlConfig:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',exclude:!f,existsSelected:!f,fieldName:geo.src,searchTechnique:prefix,selectedOptions:!(US),sort:(by:_count,direction:desc),title:'Source%20Country'),grow:!t,id:'612f8db8-9ba9-41cf-a809-d133fe9b83a8',order:0,type:optionsListControl,width:small),(controlConfig:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',exclude:!f,existsSelected:!f,fieldName:machine.os.keyword,searchTechnique:prefix,selectedOptions:!(osx,'win%207','win%208',ios),sort:(by:_count,direction:desc),title:OS),grow:!t,id:'9807212f-5078-4c42-879c-6f28b3033fc9',order:1,type:optionsListControl,width:small),(controlConfig:(dataViewId:'90943e30-9a47-11e8-b64d-95841ca0b247',fieldName:bytes,step:1,title:Bytes,value:!('6696','14567')),grow:!t,id:'6bf7a1b4-282e-43ac-aa46-81b97fa3acae',order:2,type:rangeSliderControl,width:small)),ignoreParentSettings:(ignoreFilters:!f,ignoreQuery:!f,ignoreTimerange:!f,ignoreValidations:!f),labelPosition:oneLine),references:!((id:'90943e30-9a47-11e8-b64d-95841ca0b247',name:'controlGroup_612f8db8-9ba9-41cf-a809-d133fe9b83a8:optionsListDataView',type:index-pattern),(id:'90943e30-9a47-11e8-b64d-95841ca0b247',name:'controlGroup_9807212f-5078-4c42-879c-6f28b3033fc9:optionsListDataView',type:index-pattern),(id:'90943e30-9a47-11e8-b64d-95841ca0b247',name:'controlGroup_6bf7a1b4-282e-43ac-aa46-81b97fa3acae:rangeSliderDataView',type:index-pattern)),viewMode:edit)
    `
  </details>

### Checklist

- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [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
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/10172
-
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/10186
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

## Release note

Controls are now available as a panel type, which means that they can be
freely placed anywhere in your Dashboards! The output filters are
limited to their sections, which allows you to target only a subset of
panels with a given control. If desired, controls can still be pinned to
the top of the Dashboard with a global scope.

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Zac Xeper <Zacqary@users.noreply.github.com>
Co-authored-by: Catherine Liu <catherine.liu@elastic.co>
Co-authored-by: Zacqary Xeper <zacqary.xeper@elastic.co>
Co-authored-by: Stratou <efstratia.kalafateli@elastic.co>
Co-authored-by: Davis McPhee <davis.mcphee@elastic.co>

## Summary

When resolving merge conflicts with
elastic#245310 in the [Controls Anywhere
PR](elastic#245588), we accidentally
ended up with control references being spread twice. This PR undoes
that.

…aved changes (#248029)

## Summary

This PR ensures that **only** the necessary pieces of layout state are
backed up when a dashboard has unsaved changes. Specifically, it fixes
two separate bugs with backup state:

1. Consider the following code:


https://github.com/elastic/kibana/blob/18f8010cd26a8fa6abe3dc844d199ca52dcd122d/src/platform/plugins/shared/dashboard/public/dashboard_api/unsaved_changes_manager.ts#L125-L128

Because #245588 made pinned
controls **normal children** of the Dashboard rather than having
separate unsaved changes management through the control group, the above
code resulted in **panels** being backed up as unsaved changes **even
if** only controls had changes. For example, making a single selection
in a control resulted in both controls **and** panels being backed up to
session storage - which caused extremely long URLs when `Short URL`
permissions were turned off.

2. Now consider the following:


https://github.com/elastic/kibana/blob/18f8010cd26a8fa6abe3dc844d199ca52dcd122d/src/platform/plugins/shared/dashboard/public/dashboard_api/unsaved_changes_manager.ts#L83-L88


https://github.com/elastic/kibana/blob/18f8010cd26a8fa6abe3dc844d199ca52dcd122d/src/platform/plugins/shared/dashboard/public/dashboard_api/layout_manager/layout_manager.ts#L492-L517

Because we were using `isLayoutEqual`, which is checking for layout
changes to **both** controls and panel layouts, we were reporting layout
changes for panels even if only controls changed. For example,
reordering a single control resulted in both controls **and** panels
being backed up to session storage - which caused extremely long URLs
when `Short URL` permissions were turned off.

This PR fixes both of these bugs by...

1. We now compare **which children actually changed** and determine
which ones are controls and which are normal panels. We only backup
panels if at least one panel child changed, and same with controls.

2. We now separate out our comparison into `arePanelLayoutsEqual` and
`areControlsLayoutsEqual` and we conditionally return each piece of
state as unsaved depending on the results.

### 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
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

---------

Co-authored-by: Nathan Reese <reese.nathan@gmail.com>

…aved changes (elastic#248029)

## Summary

This PR ensures that **only** the necessary pieces of layout state are
backed up when a dashboard has unsaved changes. Specifically, it fixes
two separate bugs with backup state:

1. Consider the following code:


https://github.com/elastic/kibana/blob/18f8010cd26a8fa6abe3dc844d199ca52dcd122d/src/platform/plugins/shared/dashboard/public/dashboard_api/unsaved_changes_manager.ts#L125-L128

Because elastic#245588 made pinned
controls **normal children** of the Dashboard rather than having
separate unsaved changes management through the control group, the above
code resulted in **panels** being backed up as unsaved changes **even
if** only controls had changes. For example, making a single selection
in a control resulted in both controls **and** panels being backed up to
session storage - which caused extremely long URLs when `Short URL`
permissions were turned off.

2. Now consider the following:


https://github.com/elastic/kibana/blob/18f8010cd26a8fa6abe3dc844d199ca52dcd122d/src/platform/plugins/shared/dashboard/public/dashboard_api/unsaved_changes_manager.ts#L83-L88


https://github.com/elastic/kibana/blob/18f8010cd26a8fa6abe3dc844d199ca52dcd122d/src/platform/plugins/shared/dashboard/public/dashboard_api/layout_manager/layout_manager.ts#L492-L517

Because we were using `isLayoutEqual`, which is checking for layout
changes to **both** controls and panel layouts, we were reporting layout
changes for panels even if only controls changed. For example,
reordering a single control resulted in both controls **and** panels
being backed up to session storage - which caused extremely long URLs
when `Short URL` permissions were turned off.

This PR fixes both of these bugs by...

1. We now compare **which children actually changed** and determine
which ones are controls and which are normal panels. We only backup
panels if at least one panel child changed, and same with controls.

2. We now separate out our comparison into `arePanelLayoutsEqual` and
`areControlsLayoutsEqual` and we conditionally return each piece of
state as unsaved depending on the results.

### 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
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

---------

Co-authored-by: Nathan Reese <reese.nathan@gmail.com>

## Summary

Just a couple of minor cleanups I've been meaning to do after the
controls anywhere #245588 PR merged, mainly pulling the
`addPanelFromLibrary` out of the plugin file.

### Checklist

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [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
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

---------

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

## Summary

Just a couple of minor cleanups I've been meaning to do after the
controls anywhere elastic#245588 PR merged, mainly pulling the
`addPanelFromLibrary` out of the plugin file.

### Checklist

- [ ] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
- [ ] [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
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)
- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
- [x] Review the [backport
guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing)
and apply applicable `backport:*` labels.

---------

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

…_panels (#254999)

## Summary

The APM service metrics tab crashes when loading the static JSON
dashboard because the dashboard plugin's `DashboardState` no longer has
a `controlGroupState` property — controls are now represented as
`pinned_panels`.

**Caused by:** [Controls Anywhere] Feature Branch —
#245588

That PR refactored the entire controls system, removing the
`controlGroup` embeddable and replacing `controlGroupState` with
`pinned_panels` in `DashboardState`. The APM
`static_dashboard/index.tsx` was updated to use the new
`controlGroupStateBuilder` API signature (adding the `uiActions` param),
but the fundamental issue was missed: the `controlGroupState` object
built by the builder is no longer consumed by the dashboard. The
`getInitialInput()` return value spreads into `DashboardState`, which
silently ignores the `controlGroupState` property — or worse, the
`controlGroupStateBuilder.addDataControlFromField()` call throws during
control type detection via `uiActions`, causing `getCreationOptions` to
fall into the catch block and return empty options (no panels rendered
at all).

A follow-up PR ([Dashboards as Code] `snake_case` controls schemas —
#249300) snake_cased the field
names in the builder call but didn't address the underlying issue.

**Fix:**
- Replace the `controlGroupStateBuilder` + `controlGroupState` pattern
with a direct `pinned_panels` array in the new format
- Add `useControlsIntegration: true` to `DashboardCreationOptions` so
the controls render
- Remove the now-unused `@kbn/control-group-renderer` dependency and
`UiActionsStart` parameter

### Changes
-
`x-pack/solutions/observability/plugins/apm/public/components/app/metrics/static_dashboard/index.tsx`
— migrated controls from `controlGroupState` to `pinned_panels`
-
`x-pack/solutions/observability/plugins/apm/public/components/app/metrics/static_dashboard/index.test.tsx`
— added Jest tests for `getCreationOptions` contract
- `x-pack/solutions/observability/plugins/apm/tsconfig.json` — replaced
`@kbn/control-group-renderer` reference with `@kbn/controls-constants`

## Test plan
- [x] Navigate to an APM service with a known runtime dashboard (e.g.
Java, Node.js) → Metrics tab
- [x] Verify the "Node name" options list control renders above the
dashboard
- [x] Verify dashboard panels load without errors
- [x] Verify filtering by node name works correctly
- [x] Jest tests pass

---------

Co-authored-by: Cursor <cursoragent@cursor.com>