Draft: Associate Item Frontend

[floriangantner]

References

Add references/links to any related issues or PRs. These may include:

• Fixes #[issue-number](https://github.com/4Science/DSpace/issues/365) (if this fixes an issue ticket) Associate some project to some publication DSpace#365
• Requires DSpace/DSpace#pr-number (if a REST API PR is required to test this)

Description

basic functionality to associate two items. own page with search and list preview with action buttons, services to trigger. associateitemmodes are being used to check the access to the page and to show the context-menu button. In the majority some adoption of the edititem, edititem-mode and edit-relationship functionality.

Instructions for Reviewers

Please add a more detailed description of the changes made by your PR. At a minimum, providing a bulleted list of changes in your PR is helpful to reviewers.

List of changes in this PR:

• First, ...
• Second, ...

Counterpart Backend:
4Science/DSpace#382

Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.

• based on the default configuration (see backend PR Draft: AssociateItem Backend DSpace#382) the following steps can be performed:
• Open project where the logged in user profile is in cris.investigator field
• Wait for context-menu button to be shown
• Open Button
• Associate some publications and disassociate some publications
• See result of the actions in the regarding relation tab of the publication.
• Test the scenario with further conditions

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• 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 yarn lint
• My PR doesn't introduce circular dependencies (verified via yarn 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.
• 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.