feat (3320): add Documentation link to Admin Sidebar

[guillermo-escire]

References

Fixes #3320

Description

This PR adds a "Documentation" link to the Admin Sidebar menu. The link URL is automatically generated based on the DSpace backend version, and can also be customized via configuration.

Instructions for Reviewers

List of changes in this PR:

• Created DocumentationMenuProvider that reads dspaceVersion from the REST API root endpoint, extracts the major version, and builds the documentation URL dynamically (e.g. DSpace 10.0.0 → https://wiki.lyrasis.org/display/DSDOC10x)
• Added configurable documentationUrl property so sites can override the default URL with their own custom documentation link
• Modified AdminSidebarSectionComponent (.ts and .html) to support MenuItemType.EXTERNAL links with target="_blank" rendering
• Added external link icon (fa-external-link-alt) next to external links in the sidebar
• Changed visibility to visible: true so all users with access to the Admin Sidebar can see the Documentation link (not only Site Administrators)
• Registered the new provider in app.menus.ts under MenuID.ADMIN
• Added i18n key menu.section.documentation in en.json5

How to test:

1. Log in as any user with access to the Admin Sidebar
2. Verify the "Documentation" link appears in the Admin Sidebar with a book icon and external link icon
3. Click on "Documentation" and verify it opens the correct DSpace documentation wiki in a new tab
4. Verify the URL matches the major version of your DSpace backend
5. Set documentationUrl in your config and verify it overrides the default URL

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.

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.

[guillermo-escire]

Hi @tdonohue , as discussed, the previous PR #5077 was affected by the PolinRider malware on Jorge's account.

I have cleaned up all the changes and created a new PR from a clean repository. The new PR also addresses all the feedback from @MMilosz (visible: true for all admin sidebar users, external link icon, and configurable documentation URL). Please review the new PR instead. Sorry for the inconvenience.

[github-actions]

Hi @guillermo-escire,
Conflicts have been detected against the base branch.
Please resolve these conflicts as soon as you can. Thanks!

[github-actions]

Hi @guillermo-escire,
Conflicts have been detected against the base branch.
Please resolve these conflicts as soon as you can. Thanks!

[alexandrevryghem]

I haven't tested this PR, but I noticed this PR removed these 2 providers, could you please restore them?