[DSpace-CRIS] Porting of Bulk Import functionality

[FrancescoMolinaro]

References

Relates to: DSpace/DSpace#11749
Relates to: Feature Differences #25

Description

Add new /bulk-import path under the collection route, to execute an import in bulk from file directly into the
collection.
The new page is accessible from the collection edit menu:

Instructions for Reviewers

The bulk import script allows to add, update or delete multiple items by uploading an excel file with a specific structure. All the items involved in a single import run must refer to a single collection: the updated and deleted objects must therefore be contained in that collection and the added items will be placed within the same collection.

List of changes in this PR:

Add new collection subroute and related page component.
Add new collection edit menu.

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
• My PR passes ESLint validation using npm run lint
• My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
• My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
• My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
• My PR aligns with Accessibility guidelines if it makes changes to the user interface.
• My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
• My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
• If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.

[tdonohue]

Same here, @FrancescoMolinaro . Please specify in the description which features/differences this PR relates to.