Add Adobe Dynamic Media with OpenAPI image provider support

[stefashkaa]

Feature Title

Add Adobe Dynamic Media with OpenAPI image provider support

Description

Add an Adobe Dynamic Media with OpenAPI provider for public approved asset delivery. Its endpoint and access model differ from Dynamic Media Classic / Scene7 #16

Use Case

An application receiving approved Adobe asset delivery URLs needs responsive sizes and explicit supported output formats through the shared image API.

Proposed Solution

• Add and export adobeDynamicMedia through the core provider registry so Angular, React, and Svelte can use the shared configuration.
• Support /adobe/assets/{assetId}/as/{seoName}.{format} URLs with documented width, height, quality, and offering-specific controls.
• Preserve the asset ID, SEO name, hostname, and unrelated parameters. When requesting an explicit format, apply auto-format=false where required by the documented delivery behavior.
• Limit initial support to public approved assets. Restricted delivery requiring authorization headers needs an application delivery path and cannot be implemented by returning an ordinary image URL alone.
• Add setup documentation and focused fixtures covering asset identity, extension and auto-format interaction, supported modifier limits, and public-asset scope. Validate advertised dimensions and content types against an enabled service or controlled server where applicable.

Alternatives Considered

Prepare Adobe delivery URLs in application code or use a custom provider. A Scene7 adapter targets a different API and does not cover this delivery contract.

Examples from Other Libraries

• Not found
• Dynamic Media OpenAPI delivery APIs
• Explicit formats and auto-format behavior