Dependent metadata fields not visible or mappable in metadata configuration.

Problem/Motivation

After migrating from the legacy Media: Acquia DAM module to the Acquia DAM module, dependent metadata fields from Acquia DAM (for example, Credit-copyright) are no longer:

• visible in the Drupal metadata configuration UI at /admin/config/acquia-dam/metadata, and
• returned by the /v2/metadata/fields/viewable endpoint the Drupal module relies on.

In the legacy media_acquiadam module, these dependent fields were exposed and could be mapped to Drupal fields. This seems as a regression in available functionality after moving to the new module.

Proposed resolution

We propose two possible approaches to address this limitation:

Option 1: Override with V1 API (full switch)

• Update existing method in the module to fetch metadata field definitions from the Widen V1 endpoint (`/api/rest/metadata/types`) using the customer’s domain.
• Update all internal calls to use this V1 endpoint instead of the current V2 endpoint.
• Normalize the V1 response to match the V2 structure so downstream code remains stable.
• This would be a hard switch: all sites would use V1 going forward.

Option 2: Provide both V1 and V2, let user select

• Add a configuration option (e.g., a dropdown in the metadata config form) allowing site admins to choose between V1 and V2 endpoints for metadata field discovery.
• Default to V2 for existing installs to avoid regressions; new installs can choose as needed.
• Both code paths are maintained, and the selected version is used throughout the module.