Fixed: Custom fields naming in Assets API docs

We fixed an issue where custom fields appeared in some Assets API endpoints as customColumnsFields, which didn’t match the actual API response.

Custom fields are now documented as customFields across the affected Assets API endpoints, such as Get list of assets, keeping the docs aligned with the response structure returned by the API.