docs: introduce docs on how to deploy to the platform, and help page for the licensing tool

[oemebamo]

closes https://github.com/TimefoldAI/timefold-solver-enterprise/issues/738
closes https://github.com/TimefoldAI/timefold-license-tool/issues/100

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[larsbeck]

Review

Docs-only PR — reads well and content feels accurate. Main issues are cross-doc inconsistencies in copy-paste code examples. No blockers, but a few worth fixing before merge.

Likely bugs / inconsistencies

1. Contradicting score types for the same Timetable example (high)

• constraint-overrides.adoc: ConstraintWeightOverrides<HardMediumSoftScore> + HardMediumSoftScore.ofHard/ofSoft
• rest-api.adoc: TimetableConvertor implements ModelConvertor<HardSoftScore, ...>

Same School Timetabling model, two different score types. HardMediumSoftScore is used but there's no .ofMedium anywhere, so it looks like it should be HardSoftScore (matching rest-api and the service quickstart). One of these is wrong.

--> @oemebamo It should be HardMediumSoftScore to keep it consistent.

2. Config property prefix mismatch (model-metadata.adoc, medium)

• identity: timefold.application.description, timefold.model.maturity-level
• default profile: ai.timefold.model.default-config.*

The ai. prefix on default-config vs plain timefold. on the others is suspicious. Worth double-checking one isn't a typo — mismatched prefixes silently fail to bind.

--> @oemebamo These properties are actually correct, but they do indeed look inconsisent. I don't see why they should be, so this could be a ticket.

Minor / style

• demo-data.adoc: the inserted ModelRequest two-constructor paragraph feels topically misplaced on the demo-data page; it reads more like rest-api.adoc material.
• URL inconsistency: getting-started says platformUrl is typically https://app.timefold.ai; README example uses https://api.timefold.example. Expected placeholder, but worth aligning.
• .pem claim (license-management.adoc): confirm the license download extension is actually .pem.