feat: Split and add extra configuration to export_data method

[deshansh]

Description

• Split the export_data function into export_data_csv and export_data_json, and added additional configuration options using kwargs

Issues

• Closes: Implement/document a way how to pass extra configuration to json.dump() #526

Testing

• Added test to check the export functionally as well for extra configurations

Checklist

• CI passed

[vdusek]

Thanks for the contribution! I have a few comments...

Regarding the removal of export_data, I'm not sure we should do that. Removing it would break parity with the JS Crawlee and introduce a breaking change (in which case, you'd need to use the feat! commit prefix).

Maybe we can keep the export_data and call the appropriate methods within it, like this:

async def export_data(
    self,
    path: str | Path,
    *,
    content_type: Literal['csv', 'json'] = 'csv',
    dataset_id: str | None = None,
    dataset_name: str | None = None,
    **kwargs: Any,
) -> None:
    if content_type == 'csv':
        self.export_data_csv(path, dataset_id=dataset_id, dataset_name=dataset_name, **kwargs)
    elif content_type == 'json':
        self.export_data_json(path, dataset_id=dataset_id, dataset_name=dataset_name, **kwargs)
    else:
        raise ValueError(f'Unsupported content type: {content_type}.')

[vdusek]

LGTM

[souravjain540]

hi @deshansh can you please send me your email or ping me on apify discord?