[DSpace-CRIS] Share links via social networks

[pzlakowski]

References

Fixes DSpace/DSpace#11781

Description

This PR ports social networks feature from DSpace-CRIS

We might need to adjust the wiki page too.

Instructions for Reviewers

List of changes in this PR:

• Ports share social links from CRIS
• Fixes the feature due to breaking changes in AddToAny library

Instructions to test this PR:

1. Enable social links since they are disabled by default

config/config.development.yml

# ...

addToAnyPlugin:
  scriptUrl: "https://static.addtoany.com/menu/page.js"
  socialNetworksEnabled: true
  buttons:
    - facebook
    - twitter
    - linkedin
    - email
    - copy_link
  showPlusButton: true
  showCounters: true
  title: DSpace demo

2. Visit home page, search page and item page
   • these are the only pages which use this feature in DSpace-Cris, the metadata showSocialButtons boolean needs to be added in routes for parent definition

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.