fix(AppResources): default SpAppResource.description to name on creation

[foozleface]

Summary

The "New Resource" flow in AppResources/Create.tsx constructs an SpAppResource without a description, so the row is persisted with Description = NULL. The backend report_runner create path already defaults description = name; this PR makes the frontend match.

Specify 6 hard-fails when opening a label whose underlying spappresource.Description is NULL, so any site still running S6 alongside S7 hits this immediately. Reported as Specify support ticket #824 — Grant confirmed the analysis and asked for a PR.

Changes

• Extract buildNewAppResource() helper in Create.tsx; defaults description: name.trim()
• Export the helper via exportsForTests (same pattern as getUrl in this file)
• Add a unit test asserting the new resource has description === name.trim()

Note for sites running both S6 and S7

If you already have rows with Description IS NULL, S6 will still hard-fail on them after this PR is merged — this fix only prevents new NULL rows. A one-time backfill is safe and cheap (description is a simple text label, free-form):

-- Run once per Specify database; backfills any historic NULL descriptions
-- so Specify 6 stops crashing on labels created by Specify 7.
UPDATE spappresource SET Description = Name WHERE Description IS NULL;

Test plan

• npx jest --testPathPattern CreateAppResource — 4/4 pass (3 existing + 1 new)
• Manually create a new App Resource via User Tools → App Resources → New Resource and confirm spappresource.Description is non-NULL in the DB
• Open the new resource as a label/report in Specify 6 and confirm it no longer crashes

[Iwantexpresso]

• npx jest --testPathPattern CreateAppResource — 4/4 pass (3 existing + 1 new)
• Manually create a new App Resource via User Tools → App Resources → New Resource and confirm spappresource.Description is non-NULL in the DB
• Open the new resource as a label/report in Specify 6 and confirm it no longer crashes

jest test results

Whenever the resource created the description field for the spappresource is currently staying as null. I have tried with creating 3 different app resources so far. I am a little unsure how request changes would whirl for this pr but I assume it wouldn't hurt just placing this in as one for now