Fix discoverworthy.com.managed-hosting: APEXCNAME -> CNAME (hostRequired) for Cloudflare

[travis-sansome-discoverworthy]

Description

Bug fix to the existing discoverworthy.com.managed-hosting template (added in #1110).

The apex record was APEXCNAME. Cloudflare does not support the APEXCNAME
custom record type and rejects it during Domain Connect onboarding (confirmed
by the Cloudflare Domain Connect maintainer). Cloudflare auto-applies CNAME
flattening at the zone apex, so the correct primitive is a standard CNAME.

Per the Domain Connect schema, a CNAME at host: "@" requires the template
to also set "hostRequired": true. This PR therefore:

• replaces the apex APEXCNAME with a single CNAME at host: "@",
• adds "hostRequired": true,
• drops the separate www CNAME (under hostRequired the request host is
  the subdomain, so a hardcoded www record would mis-apply as
  www.<host>.<domain>),
• removes the optional variableDescription (not required; its only purpose
  was describing %target%, which description already conveys),
• bumps version 1 → 2 (template modified after being merged).

The resulting shape is identical to the already-merged
magicpages.co.website-cname.json. The record resolves to the customer's
hosting target supplied via the signed %target% variable.

Type of change

• New template
• Bug fix (non-breaking change which fixes an issue in the template)
• New feature (non-breaking change which adds functionality to the template)
• Breaking change (fix or feature that would cause existing template behavior to be not backward compatible)

How Has This Been Tested?

• Template functionality checked using Online Editor
• Template file name follows the pattern <providerId>.<serviceId>.json
• resource URL provided with logoUrl is actually served by a webserver (N/A — template sets no logoUrl)

Checklist of common problems

• syncPubKeyDomain is set (discoverworthy.app) — mandatory, present
• warnPhishing is not set alongside syncPubKeyDomain
• syncRedirectDomain — N/A, synchronous flow uses no redirect_uri
• no TXT record contains SPF content — the template has no TXT records
• txtConflictMatchingMode — N/A, no TXT records
• hostRequired: true is set (required by the schema for a CNAME at host @)
• no variable used as a bare full record value — %target% is the pointsTo of a type-constrained CNAME record
• no bare variable used as the full host label — host is fixed (@)
• no variable used in the host field to create a subdomain; %host% does not appear in any host attribute
• essential/OnApply — N/A, the single record is required for the service to function

Online Editor test results

Editor test link:

Host set (subdomain — the only applicable case for a hostRequired template):
Test discoverworthy.com/managed-hosting example.com/test

[github-actions]

✅ JSON Filename Check Passed

[github-actions]

✅ JSON Schema Validation Passed

[github-actions]

Linter OK

discoverworthy.com.managed-hosting.json

Level	Code	Note

[github-actions]

PR Description Check Passed

All required sections are filled in correctly.

Details

  OK  Type of change: 1/4 checkboxes ticked
  OK  How Has This Been Tested?: all 3 checkboxes ticked
  OK  Checklist of common problems: 10/10 checkboxes ticked
  OK  Online Editor test results: 1 link(s) found
  OK  Template coverage: all 1 template(s) covered
Labels to remove: Checklist of common problems not complete, Forged editor links, PR description incomplete, Test links missing

PR description check PASSED