🎁 Add export functionality to grids

## Description

Cato has requested the addition of an "Export to Excel" button for the reports. Currently, this feature is considered too costly because AG-Grid does not support exporting paginated data, necessitating custom functionality to enable this.

Loop already has an option to export to Excel, but its implementation is highly specific and would require significant rework to be applicable to other reports.

### Tips
Frontend Guidelines

- [Spacing](https://docs-procosys-one-team-docs-prod.radix.equinor.com/solution/user-experience/spacing-guidelines/)
- [Error messages](https://fusion-docs.fusion-dev.net/docs/i-want-to-create/ux-design-guidelines/design_n_components/error_message/)
- [Empty states](https://fusion-docs.fusion-dev.net/docs/i-want-to-create/ux-design-guidelines/design_n_components/empty_state)
- [AG Grid](https://fusion-docs.fusion-dev.net/docs/i-want-to-create/ux-design-guidelines/design_n_components/ag_grid)

Branch and PR linking

Create a development branch in the applicable repo directly from the issue. This will automatically **link any PRs** to this issue and visualize linked PRs on the issue in the Project Board. You can also link it to an existing branch or pull request.

Project Fields

The issue is automatically added to the Project board. Verify that the Project fields are filled out where applicable.

Sub Issues

- Consider splitting the Feature up into relevant activities which are manageable within a sprint. This avoids having a feature open for a long time. Use the relevant templates for the sub-activities, e.g. Research, Design, Frontend, Backend,
- Allocate the sub-features into the sprint, not the parent feature.
- Make sure a feature has the overall responsibility of the Verification of the main Feature, e.g. the Frontend sub-issue will cover UAT.