System setting for documentation url

[josegar74]

Currently the documentation URL is hardcoded in Javascript code. In this change a new system setting is added, to allow customising the documentation URL.

This is useful to self host the documentation, applying custom branding.

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation

[jodygarnett]

This configuration change makes sense to me, may I also ask for an option for "online help" (it can be a separate PR), for links referencing https://docs.geonetwork-opensource.org/stable/help/ or embedded /doc/ which should be included with the geonetwork.war.

Including embedded docs was a long standing feature of the maven build which I fixed recently.

[jodygarnett]

Request change from /stable/ to /{version}/

[jodygarnett]

This looks correct!

[geonetworkbuild]

The backport to 4.2.x failed:

The process '/usr/bin/git' failed with exit code 1

stderr

error: could not apply 6abe90708e... System setting for documentation url
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

stdout

Auto-merging web-ui/src/main/resources/catalog/locales/en-admin.json
Auto-merging web/src/main/webapp/WEB-INF/classes/setup/sql/data/data-db-default.sql
CONFLICT (modify/delete): web/src/main/webapp/WEB-INF/classes/setup/sql/migrate/v443/migrate-default.sql deleted in HEAD and modified in 6abe90708e (System setting for documentation url).  Version 6abe90708e (System setting for documentation url) of web/src/main/webapp/WEB-INF/classes/setup/sql/migrate/v443/migrate-default.sql left in tree.

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.2.x 4.2.x
# Navigate to the new working tree
cd .worktrees/backport-4.2.x
# Create a new branch
git switch --create backport-7782-to-4.2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 6abe90708e03d6dc560997e1e8b4e74597cc9301,6fd929d139c98636e80aa1e4d0097787b57a287b,b7004f93452c200c81cb19d931a8f67849ea22c0
# Push it to GitHub
git push --set-upstream origin backport-7782-to-4.2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.2.x

Then, create a pull request where the base branch is 4.2.x and the compare/head branch is backport-7782-to-4.2.x.