[GEOS-11221] mkdocs

[jodygarnett]

Proposal: GSIP-221

• migrated markdown user guide documentation
• mkdocs.yml configuration
• source remains unchanged to allow mkdocs_translate script to be reused to correct specific files
• Fix reported migration problems
• build.xml update to call mkdocs

GSIP-221 pull-requests

main:

• [GEOS-11221] mkdocs #7462
• [GEOS-11221] mkdocs preflight rst fixes #7429

2.25.x:

• [Backport 2.25.x] [GEOS-11221] mkdocs

2.24.x:

• [Backport 2.24.x] [GEOS-11221] mkdocs preflight rst fixes #7461
• [Backport 2.24.x] [GEOS-11221] mkdocs

Checklist

• I have read the contribution guidelines.
• I have sent a Contribution Licence Agreement (not required for small changes, e.g., fixing typos in documentation).
• First PR targets the main branch (backports managed later; ignore for branch specific issues).
• All the build checks are green (see automated QA checks).

For core and extension modules:

• New unit tests have been added covering the changes.
• Documentation has been updated (if change is visible to end users).
• The REST API docs have been updated (when changing configuration objects or the REST controllers).
• There is an issue in the GeoServer Jira (except for changes that do not affect administrators or end users in any way).
• Commit message(s) must be in the form [GEOS-XYZWV] Title of the Jira ticket.
• Bug fixes and small new features are presented as a single commit.
• Each commit has a single objective (if there are multiple commits, each has a separate JIRA ticket describing its goal).

[aaime]

There are still many pages with "problems" marked in the sheet here (aka known problems):
https://docs.google.com/spreadsheets/d/1HMqUpTirEwwSQfeNYikPjU0aFMl0-W4Xj44cg8V_VJA/edit#gid=0

[jodygarnett]

There are still many pages with "problems" marked in the sheet here (aka known problems): https://docs.google.com/spreadsheets/d/1HMqUpTirEwwSQfeNYikPjU0aFMl0-W4Xj44cg8V_VJA/edit#gid=0

Yes I indicated in email I would fix reported problems first, added to checklist

[jodygarnett]

discussion actions since this missed the release candidate window:

• remove the generated markdown results
• would allow this PR can focus on cleaning up the rst files so we get a clean conversion