Show Shared Submission menu even if user is not submitter

[AdamF42]

References

• Related to #5384
• Related to [#12418] ("Shared Submissions" feature update for authors DSpace#12418)
• Related to DSpace/DSpace#5145 (Shared Submissions feature)

Description

Simple update to show "Shared Submission" items menu even if user is not submitter.

How to test

1. Log-in as simple author (the user should not be in any submission/admin group)
2. Verify that in MyDSpace dashboard you should be able to see the "Shared submission" option

Checklist

• 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]

👍 Thanks @AdamF42 ! Tested this with the backend. This small PR appears to be working, but I've found a few small issues on the backend that I'll report shortly.

I'll wait to merge this frontend PR until the backend is also working.