Preserve authorization expiry in payment extension configs

[jenny-codes]

WHY are these changes introduced?

Shopify CLI's payment extension schemas don't recognize the optional enforce_authorization_expiry field. When the field is present in shopify.extension.toml, schema parsing strips it before the deploy configuration is generated.

This prevents payment extensions from preserving their configured authorization-expiry behavior during deployment. The field remains optional, so existing extensions keep their current behavior when it is omitted.

WHAT is this pull request doing?

Implementation

• Adds a reusable AuthorizationExpirySchema for enforce_authorization_expiry.
• Applies it to credit card, custom credit card, custom onsite, and offsite payment extensions.
• Preserves the field in both directions:
  • shopify.extension.toml -> deploy configuration
  • existing draft or published configuration -> generated TOML
• Adds schema and transformation coverage for all four extension types.
• Adds a minor changeset for the new optional manifest field.

This PR only updates CLI schema validation and configuration transformation. It does not change authorization-expiry defaults, enable the option for existing extensions, or add it to redeemable or card-present extensions.

How to test your changes?

pnpm vitest run \
  packages/app/src/cli/models/extensions/specifications/payments_app_extension_schemas/base_payments_app_extension_schema.test.ts \
  packages/app/src/cli/models/extensions/specifications/payments_app_extension_schemas/credit_card_payments_app_extension_schema.test.ts \
  packages/app/src/cli/models/extensions/specifications/payments_app_extension_schemas/custom_credit_card_payments_app_extension_schema.test.ts \
  packages/app/src/cli/models/extensions/specifications/payments_app_extension_schemas/custom_onsite_payments_app_extension_schema.test.ts \
  packages/app/src/cli/models/extensions/specifications/payments_app_extension_schemas/offsite_payments_app_extension_schema.test.ts \
  packages/app/src/cli/services/payments/extension-config-builder.test.ts

Result: 67 tests passed. Repository lint and type checks also passed.

Checklist

• I've considered possible cross-platform impacts. This is platform-independent schema and object transformation code.
• I've considered possible documentation changes. The new field may require payment-extension documentation after release.
• I've considered analytics changes. No analytics changes are required.
• The change is user-facing. It adds a backward-compatible optional manifest field and includes a minor changeset.