Let the request form capture every objectType it offers

[stiebitzhofer]

Summary

The dictionary-request dropdown offers eight objectTypes. The form could complete four.

schema/dictionary-entry.schema.json requires a field per kind; the form asked for two of them:

objectType	schema requires	form asked?
SingleValuedDataElement / MultiLanguageDataElement / RelatedResource	valueDataType	yes
DataElementCollection	elements	yes — "Collection members"
MultiValuedDataElement	itemType	no
MeasurementUnit	symbol	no
MeasurementUnit	crossReferences.ucumCode	no
Quantity	dimension	no
Value	value	no

A requester could pick MeasurementUnit, fill in everything asked of them, and still submit a request that cannot be drafted. The form's header promises it mirrors the envelope "so triage can generate the draft YAML mechanically" — for half the kinds it could not. ucumCode is the sharpest case: check 2 validates its syntax, so a guess fails the publish PR rather than degrading quietly.

Change

The five missing inputs, as one group behind a note saying only the row matching your objectType applies. All stay required: false — GitHub issue forms cannot express "required when that dropdown says X" — so the condition lives in each label and description.

ucumCode's help text warns that UCUM is case-sensitive and spells some units unexpectedly (Cel, [psi], mm2), and tells the requester to leave it blank rather than guess.

Left out uneceCommonCode, qudtUnit and conversions. Real unit entries carry them, but they are registry lookups a maintainer does better than a requester, and none is schema-enforced. Drafting fills them.

Ratchet

This is the second time the form has trailed the schema, so it becomes a check rather than a thing to remember. test/request-form.test.ts walks the schema's allOf conditionals and asserts every conditionally-required property has an input to capture it — and, in reverse, that no input names a field the envelope lacks, since that produces a value with nowhere to go.

Adding a kind-specific requirement to the schema now fails the suite until the form can ask for it.

Closes #114

Test plan

• npm test — 82/82
• Form YAML parses: 24 blocks, 22 inputs, all five new ids present
• Ratchet verified by breaking it: renamed ucum-code in the form and confirmed both directions fail, naming the gap — MeasurementUnit requires crossReferences.ucumCode — no form input "ucum-code" — then restored and re-ran green. A guard that has only ever passed proves nothing.
• Caught a bug in my own test while writing it: crossReferences is a $ref into $defs, so the reverse check was reading an empty property set. Now resolves the ref, with an assertion that it did.
• new-entry skill's field list updated to match, so drafting knows to look for the new block

Note

Found while answering "did the form adopt the legal reference?" — it had, in #78's own commit (d10ca65), with an ELI placeholder and wording that separates it from definitionStandard/testStandard. These five had not.