Publish Wiki directly and stop recreating its submodule during sync #365

The old consumer Wiki caller references a workflow that no longer declares workflow_call, so nine library workflows fail before running any jobs. Container fixed the same failure by generating with read-only permissions and publishing to the separate Wiki repository without a tracked submodule.

Adopt that direct-publication model as a shared DevTools workflow and a short packaged caller. Normal dev-tools:sync must generate local Markdown without invoking wiki --init, otherwise consumers recreate the deleted submodule on their next synchronization.

Acceptance:

• PRs generate Markdown without Wiki write credentials; only main publishes.
• Publish through a separate checkout, preserve manual pages outside generated namespaces, and reject invalid payloads and stale source revisions.
• Remove the repository Wiki gitlink and its matching .gitmodules entries, retaining the remote Wiki/history.
• Preserve explicit legacy --init and legacy reusable implementations during migration, but retire automatic maintenance triggers from migrated wrappers.
• Verify normal sync, self-generation and the real publisher before opening consumer adoption PRs.

Reference: php-fast-forward/container#15.