Add detailed warnings to SSR-related configs about impact on SEO.

[tdonohue]

Description

This PR is coming out of a discussion I had with the Google Scholar team today. Google Scholar is still noticing a large number of DSpace sites that are either disabling SSR entirely, or accidentally disabling it on pages that require indexing.

This PR therefore adds inline comments next to the key SSR-related configurations which warn sites about the risk of SEO impacts if they modify the current settings in Production scenarios. This is just an attempt to ensure these warnings are documented at the place(s) where sites might be modifying their configurations...to ensure they don't overlook them.

Instructions for Reviewers

• PR only adds inline comments. No actual code added.
• Therefore, just review the comments and determine whether they are clearly written or need any updates.

[tdonohue]

Closing & reopening as tests never ran for this PR.

[EikLoe]

This looks good to me! Thanks @tdonohue

[tdonohue]

Merging with one approval as this is just code comments. We can always improve further as necessary.

[dspace-bot]

Backport failed for dspace-8_x, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin dspace-8_x
git worktree add -d .worktree/backport-6075-to-dspace-8_x origin/dspace-8_x
cd .worktree/backport-6075-to-dspace-8_x
git switch --create backport-6075-to-dspace-8_x
git cherry-pick -x 9b4a9a54644cd4255cc939285296c73e921a098f

[dspace-bot]

Successfully created backport PR for dspace-9_x:

• [Port dspace-9_x] Add detailed warnings to SSR-related configs about impact on SEO. #6112

[dspace-bot]

Successfully created backport PR for dspace-10_x:

• [Port dspace-10_x] Add detailed warnings to SSR-related configs about impact on SEO. #6113