docs(edge-delivery-services): lead five skill descriptions with their trigger

[LuizFrare]

Follow-up to #215.

Context

#215 already got its sweep. All 19 skills in its two tables were fixed on 6 July, one PR per skill (#241, #244, #245, #246, #248, #249, #250, #251, #254, #258 and siblings), and x-search has since been removed from the plugin. As far as I can tell #215 can be closed — this PR does not reopen its scope.

What it does cover is five skills in the same plugin that show the exact pattern #215 describes but were never in its tables. Four open with a capability statement instead of a trigger; content-driven-development opens with "Apply a Content Driven Development process".

Changes

Each description now follows the shape the sweep established:

Use this when <trigger>. Covers <topics>. [For <adjacent topic> use <sibling skill>.]

Skill	Old opening	New opening
aem-cli	"Reference for the Adobe AEM CLI…"	"Use this when installing, running, or configuring the Adobe AEM CLI…"
content-driven-development	"Apply a Content Driven Development process…"	"Use this when making any AEM Edge Delivery Services code change…"
create-site	"Creates a new AEM Edge Delivery site from scratch…"	"Use this when a user wants to create a brand-new AEM Edge Delivery site…"
page-import	"Import a single webpage from any URL…"	"Use this when importing or migrating a single webpage from any URL…"
ue-component-model	"Create or edit the Universal Editor component configuration…"	"Use this when the user mentions component models, component definitions…"

No information was dropped. Every scope note, trigger alias and sibling redirect already present in these descriptions is preserved — the migrate/migration/migrating aliases and the snowflake disambiguation on page-import, the da-content and content-driven-development redirects on aem-cli, the page-import redirect on create-site — only reordered so the trigger leads.

Versions are untouched; semantic-release owns those.

One commit per skill, matching both the granularity of the original sweep and each skill's own .releaserc.json.

Verification

npm run validate passes (166 skills, exit 0).

[LuizFrare]

Per CONTRIBUTING.md: this PR was co-authored with an AI tool and should carry the ai-generated label. I can't apply labels as an outside contributor — could a maintainer add it? Disclosing here in the meantime, and the commits carry a Co-Authored-By trailer.

[LuizFrare]

Same situation as #319: the workflow runs here are sitting in action_required, so validate and conventional-commits have not reported. As an outside contributor I cannot trigger them. Could a maintainer approve the runs?

The CLA check is signed and green, and npm run validate passes locally (166 skills, exit 0).

One thing worth a maintainer eye beyond the diff: #215 looks complete to me. Every skill in its two tables was fixed in the July sweep, and x-search is no longer in the plugin, so the issue can probably be closed. This PR deliberately stays outside that scope and only touches five skills that show the same pattern but were never in its tables. If those five were left as they are on purpose, say the word and I will close this.