Tribute type for CRM mappings

For GiveCampus integrations and API.

The gifts response exposes the legacy honor value and a custom_fields object built from configured additional fields. Standard tribute answers can appear as custom_fields.in_honor_of and custom_fields.in_memory_of when configured. Do not rely on a top-level tribute_type field; use the documented tribute fields for your API version.

If the destination requires one type, agree a connector mapping based on which source answer is populated, retaining the honoree name separately. Handle both-filled and neither-filled records explicitly rather than guessing. A school-specific custom tribute-type field may exist, so confirm the actual API version, form fields and redacted response. Do not rename the standard source fields merely to match a destination label.