Start to implement new UI components for GSA.

Both components are based on mantine and flexbox. They are intended to
replace Layout especially in dialogs.

All form components should be able to call the onChange handler with the
value, name pair. Therefore introduce a generic hook to abstract the
event handling.

Use latest release of userEvent.

The theme provider is required to be able to test components based on
opensight-ui and mantine.

The useDownload hook in conjunction with the Download component should
replace the withDownload HOC in future.

The ResizeObserver is required to be able to run the tests for
opensight based components.

The capabilities of the user are provided via a react context and
therefore it should be able to load them independently from the redux
store.

Using the new hooks allows to rewrite all filter dialogs to function
components more easily.

When rendering the react app the theme provider for mantine is required.

Use opensight-ui and mantine for all form components. With this change
all the form components are refreshed in their visual appearance.

Update Dialog component to use the Model component from opensight for
improved UI.

Use opensight AppNavigation to implement a new menu.

Use new AppBar from opensight.

Align the content of list pages at the top.

Use new form components for updated UI at the login page.

Adjust the DialogNotification component for new Dialog.

Adjust TrashCan page for new UI.

Adjust layout of wizard dialogs for new UI.

Fix the layout of the performance page.

Adjust create and edit dialogs for new UI components and layout.

Adjust the filter dialogs of all list pages.

Fix the CPE icon and update the menu entries to use contain necessary
object properties.

```
SyntaxError: Unexpected token 'export'
Module <snip>/node_modules/@greenbone/opensight-ui-components/lib/utils/compareHelper.js:1 seems to be an ES Module but shipped in a CommonJS package. You might want to create an issue to the package "@greenbone/opensight-ui-components" asking them to ship the file in .mjs extension or add "type": "module" in their package.json.

As a temporary workaround you can try to inline the package by updating your config:

// vitest.config.js
export default {
  test: {
    server: {
      deps: {
        inline: [
          "@greenbone/opensight-ui-components"
        ]
      }
    }
  }
}
```

Add JSDOM as direct development dependency because it is required to run
the UI unit tests. Regenerate the package lock file to remove obsolete
dependencies.

These components are obsolete since we are using the Modal component
from opensight-ui/mantine now.

This will allow to use an own language switcher component.

Actually it is optional and it is set to an empty string by default
already.

Split the required js code for opensigth-ui into an own chunk bundle for
production builds.

It seems window.matchMedia is required for the Select components now.
Thus implement a mock of the API for being able to test the select
components.

The TitleBar is not used anymore.

Get the tests for the dialog components running again, drop all
snapshots because with mantine they aren't stable anymore and improve
testing specific component parts by adding getter functions.

The getters for specific components were extracted into a testing
module.

Fix and update all powerfilter tests by adapting to new form components
and using the testing getters.

clickElement is more generic because the function allows to send a click
event on arbitrary HTML elements not only select items.

Allow for querying within a specific parent element. This will allow for
easier usage of the testing functions within pages tests where
components like select boxes may be rendered at several places.

We need to be able to test the bulk actions. Therefore is is required to
query for the table footer, the table and the check boxes within and the
bulk action icons.

Action items are icons that cause some action on use clicks.

Testing clicking on export, start and resume for the detailspage doesn't
work at the moment. The click handler is just not called.

Allow completion for expect, etc. in VS code.

It seems queryAllByRole doesn't return the desired elements under some
circumstances. Therefore use an easier query for getting the options.

Abstract fireEvent for changing the value of an input element.

The snapshot test are not very useful and prone for changes which get
applied without a deeper review.

Snapshots are flacky and not really useful.

Add testing function for easier testing the behavior of multiselect
components.

Besides getting the footer and body also allow to get the header of a
table.

When clicking on multiselects sometimes user event complained about
`pointer-events` css property being `none`. Avoid this issue by not
checking for `pointer-event` at all.

The emotion library has a check if global vi or jest is set to detect if
it is running in a testing environment. Therefore just an empty vi
object for the tests to keep it quiet.

Add a draft for toggling the language between en and de via a language
switcher in the app header.

asset-mangement is an external application and therefore internal links
can't be used.