feat: export csv

[AbhishekA1509]

Description

This pull request introduces a reusable "Export to CSV" feature for the application, allowing users to export data as CSV files through a flexible and customizable UI component. The implementation includes new components, type definitions, and integrates the necessary dependencies for CSV export functionality. Additionally, minor improvements are made to type usage and icon support.

Export to CSV Feature:

• Added a new ExportToCsv component, which provides a configurable button or trigger for exporting data to CSV. It supports custom modal dialogs, error handling, loading states, and external triggers. (src/Shared/Components/ExportToCsv/ExportToCsv.tsx, src/Shared/Components/ExportToCsv/ExportToCsv.tsxR1-R182)
• Implemented an ExportToCsvDialog component to handle export progress, errors, and manual download options within a modal dialog. (src/Shared/Components/ExportToCsv/ExportToCsvDialog.tsx, src/Shared/Components/ExportToCsv/ExportToCsvDialog.tsxR1-R84)
• Defined flexible type interfaces for the export component and dialog, supporting custom headers, API promises, and trigger configurations. (src/Shared/Components/ExportToCsv/types.ts, src/Shared/Components/ExportToCsv/types.tsR1-R72)
• Exported the new components and types for use throughout the application. (src/Shared/Components/ExportToCsv/index.ts, src/Shared/Components/ExportToCsv/index.tsR1-R2)
• Registered the export feature in the shared components index for easier imports. (src/Shared/Components/index.ts, src/Shared/Components/index.tsR56)

Dependency Updates:

• Added react-csv and its type definitions to package.json to enable CSV file generation and download. [1] [2]

Icon Support:

• Added a new "arrow line down" icon to the icon library for use in export buttons. (src/Shared/Components/Icon/Icon.tsx, [1] [2]

Type Improvements:

• Updated type usage in ResourceBrowser.Types.ts to remove unused imports and improve prop definitions for resource recommender action menus. [1] [2]

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Checklist

• The title of the PR states what changed and the related issues number (used for the release note).
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas