[CON-1527]feat(zendesk): Human-readable custom fields

[Cobalt0s]

Description

Requests and Tickets objects share the same ticket_fields as its custom fields.

The id is mapped to ticket_fields to figure out the human readable name. However, there is no good JSON type field name. Ex: "customer type", which contains a space because field name is "Customer Type".

Custom fields have interesting value options which are either stored under one of the following:

There is no good documentation on the types of custom fields. Here is the approach I took to map field types to Ampersand's ValueType:

Test

Metadata(Tickets)

Read(Tickets)

[Cobalt0s]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• [CON-1527]feat(zendesk): Human-readable custom fields #1411 👈 (View in Graphite)
• feat(zendesk): Fields Metadata V2 #1410
• feat(common): Make ParseResult use generic Record type #1321 : 5 other dependent PRs (#1320 , #1324 , #1325 and 2 others)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.