Replace plaintext links to www.dspace.org

[alanorth]

Description

We have many occurrences of plaintext HTTP links to www.dspace.org in the UI and license notices. In 2025 we should not be using plaintext links anywhere, and www.dspace.org even returns an HTTP 301 permanent redirect to the HTTPS version.

I used this command to find and replace all occurrences:

$ grep -rl 'http://www.dspace.org' * \
  | xargs sed -i 's_http://www.dspace.org_https://www.dspace.org_'

We should do the same on all other currently supported branches but the pull requests will need to be manual.

Instructions for Reviewers

Make sure the frontend still builds and runs.

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.

[tdonohue]

@alanorth : Overall, I'm in favor of the minor cleanup. But, I'm honestly hesitant to modify our DSpace license header as that is in every single Java file on the backend. So, if we modify it here, we likely need to modify every backend file.

See comment inline below

[alanorth]

Hi @tdonohue, I've adjusted this to only modify links in README.md and the footer.

[tdonohue]

Thanks @alanorth ! Overall, this looks good now. But, I found one broken link that we should correct before merging.

[tdonohue]

👍 Thanks @alanorth ! Looks good now.