Map Pipedrive V2 custom fields

[srl-git]

Tell us what you do here

• improving, documenting, or customizing an existing source

Short description

Adds optional custom field mapping for Pipedrive V2 resources.

When map_custom_fields=True is passed to pipedrive_v2_source, supported V2 resources fetch their field metadata from the corresponding V2 field endpoint and use it to rename hashed custom_fields keys into readable top-level columns. Enum and set option IDs are mapped to labels using the existing custom field mapping behavior.

The mapping is opt-in to avoid changing existing V2 destination schemas by default. Field mappings are also stored in source state, so if a Pipedrive custom field is renamed later, future loads continue writing to the original normalized column name instead of creating a new column.

Related Issues

Fixes #683

Additional Context

I have read the contributing guide and run the tests locally.

Local checks run:

• uv run pytest tests/pipedrive/test_pipedrive_source.py
• make lint-code

[dat-a-man]

it is tested once and works as expected.