[netomi]

Moves the deployment guide out of the wiki and into doc/deployment.md, and folds the separate NGINX
page into it as the HTTPS section.

Why

The wiki cannot be versioned, reviewed, or updated in the same change as the code, and it has
drifted. Comparing the ovsx.* properties the wiki documents against the ones the server actually
binds in src/main/java:

	count
properties bound in the code	179
documented in the wiki	132
bound but undocumented	66
documented but no longer in the code	15

The 66 include the entire ovsx.scanning.* family - blocklist check, namespace-ownership check,
secret detection with gitleaks - plus ovsx.cors.public-origins, the access-token hashing settings
(token-hash-algorithm, -pepper, -previous-peppers, -accept-unpeppered) and
ovsx.migrations.*.

The 15 are actively misleading: nothing under ovsx.publishing. is bound any more
(require-license, unsupported-icon-formats), and ovsx.elasticsearch.relevance.* was renamed to
ovsx.search.relevance.* but is still documented under both names. Also
ovsx.caching.extensionquery-*, ovsx.redis.embedded, ovsx.storage.cdn.*, ovsx.mirror.enabled.

In the repository a property can be documented in the pull request that adds it, and
scripts/config-properties-report.sh already lists every bound key with its default, so a CI check
that the guide and the code agree becomes possible. That check is the intended follow-up, and it
would have caught all 81 discrepancies above.

What is in this PR

Deliberately content-preserving, so that reviewing the move is not tangled up with reviewing the
corrections. Diffing the moved text against the wiki source gives exactly three changed lines, all
of them links into this repository that are now repository-relative instead of absolute to
eclipse/openvsx on master:

was	now
.../blob/master/deploy/docker/build.sh	../deploy/docker/build.sh
.../blob/master/deploy/docker/configuration/application.yml	../deploy/docker/configuration/application.yml
.../blob/master/webui/src/default/theme.tsx	../webui/src/default/theme.tsx
.../blob/master/webui/src/page-settings.ts	../webui/src/page-settings.ts

Everything else is identical, stale entries included, apart from trailing whitespace: the wiki text
carried it on 36 lines and the trim trailing whitespace hook rejects it. Most is padding in empty
table cells, and the three lines with two or more trailing spaces are each followed by a blank line,
so none was a markdown hard line break and nothing renders differently. The #oauth2, #upstream-registry and
#upstream-registry-instance anchors were checked and still resolve within the new file.

The NGINX page is folded in under ## HTTPS Configuration, its #### 1./#### 2. headings demoted
to ### so they nest. It was only ever reachable through a link at the bottom of the deployment
page, and it is the other half of the same subject.

README.md gains a pointer to the new document under "Getting Started".

What stays in the wiki

The architectural overview, along with its diagram, which lives in the wiki repository. Replacement
text for the two wiki pages is ready and should land once this merges, so that nothing points at a
file that is not yet on main:

• Deploying Open VSX keeps the overview and links here; its two in-page links to sections that
  moved are repointed at this document.
• NGINX HTTPS Configuration becomes a short pointer to doc/deployment.md#https-configuration,
  keeping its title so existing inbound links still land somewhere useful.

Follow-ups

1. Wire scripts/config-properties-report.sh into CI, so the guide cannot drift again.
2. Correct the content: the 15 stale entries, the 66 missing properties, and the reverse-proxy
   guidance. The NGINX example currently sets proxy_set_header X-Forwarded-Host $host, and $host
   is the client's Host header, so the documented reference deployment forwards a client-controlled
   value - worth fixing along with the rest.

Prepared with Claude Code.