Add destination settings and action mappings for databricks destination

[itsarijitray]

JIRA: https://twilio-engineering.atlassian.net/browse/STRATCONN-6241

Sample Instance: http://app.segment.build/mme-e2e/engage/spaces/entities-cpl-test/audiences/aud_34BRmFw6EAyFea0B8uDdg7YJ7uO/runs

Mappings preview for Databricks destination

Testing

Include any additional information about the testing you have completed to
ensure your changes behave as expected. For a speedy review, please check
any of the tasks you completed below during your testing.

• Added unit tests for new functionality
• Tested end-to-end using the local server
• [If destination is already live] Tested for backward compatibility of destination. Note: New required fields are a breaking change.
• [Segmenters] Tested in the staging environment
• [Segmenters] [If applicable for this change] Tested for regression with Hadron.

[github-actions]

New required fields detected

Warning

Your PR adds new required fields to an existing destination. Adding new required settings/mappings for a destination already in production requires updating existing customer destination configuration. Ignore this warning if this PR is for a new destination with no active customers in production.

The following required fields were added in this PR:

• Destination: Databricks, Settings:warehouseId
• Destination: Databricks, Action Field(s):event,properties,messageId,type,receivedAt

Add these new fields as optional instead and assume default values in perform or performBatch block.

[valerieernst]

lgtm!