…ntationUtil plugin (elastic#246628)

Moves the panel placement registry from the `dashboard` plugin into the
`presentationUtil` plugin. This is necessary to avoid circular
dependency issues in the [Controls Anywhere
project](elastic#245588).

Controls Anywhere introduces the concept of dashboard controls being
rendered as movable panels. For this, we need to define their
`PanelPlacementStrategy`: creating them with a very short height, medium
width, and in the top left corner of the dashboard.

This required adding the `dashboard` plugin as a `requiredPlugin` for
`controls`.

Unfortunately, elastic#245299
introduced `onechat` as a dependency to `observabilityAIAssistant`,
triggering this circular dependency cycle:

```
   │ERROR Detected circular dependencies:
   │ERROR   dashboard -> observabilityAIAssistant -> onechat -> stackConnectors -> triggersActionsUi -> controls -> dashboard
   │ERROR   triggersActionsUi -> controls -> dashboard -> observabilityAIAssistant -> onechat -> triggersActionsUi
   │ERROR   workflowsManagement -> triggersActionsUi -> controls -> dashboard -> observabilityAIAssistant -> onechat -> workflowsManagement
   │ERROR   stackConnectors -> triggersActionsUi -> controls -> dashboard -> observabilityAIAssistant -> onechat -> workflowsManagement -> stackConnectors
```

Unfortunately, Kibana architecture doesn't have a good way of moving
registries into `@kbn` packages yet, so we need to find a safer plugin
for it to live in. We determined that `controls` and `dashboard` both
depend on the `presentationUtil` plugin without incident, and it's
already a place to put other miscellaneous dashboard-related things.

- [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

---------

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