authorize-check for xlscollectionCrosswalk

[floriangantner]

References

• Fixes limit xls-collection-crosswalk to group members #422

Description

Implement interface method for fine granular check to export these crosswalks to specific groups

Instructions for Reviewers

List of changes in this PR:

• implement isAuthorized method, which was before by default true by the interface ItemExportCrosswalk
  • add group check copied from other Crosswalk Formats
• whitebox-Tests: depending on the configuration check if the crosswalk format is offered to Anonymous/Administrator users in the context-menu.
• Introduced new IntegrationTest to check the isAuthorized function
• configuration: allow access to Administrator and Anonymous (behavior as before)

	<bean class="org.dspace.content.integration.crosswalks.XlsCollectionCrosswalk" id="xlsCrosswalkCollection">
		<property name="allowedGroups">
			<list>
				<value>Administrator</value>
				<value>Anonymous</value>
			</list>
		</property>
	</bean>

Checklist

• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
• My PR passes Checkstyle validation based on the Code Style Guide.
• My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
• My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
• If my PR includes new libraries/dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR modifies REST API endpoints, I've opened a separate REST Contract PR related to this change.
• If my PR includes new configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.

[github-actions]

This pull request has been automatically marked as stale because it has not had
activity in one year. It will be closed in 14 days if no further activity occurs.

Allowing pull requests to close as stale helps us filter out old work that is no longer
relevant and helps developers focus on reviewing current work.

All pull requests closed by this bot act like normal pull requests;
they can be searched for, commented on or reopened at any point.

If these changes are still relevant then please comment and/or rebase your PR based on the
latest DSpace code. This will remove the stale status and notify us to assign a reviewer
for your PR.