FEATURE - use dbt_utils.slugify() to use issue field names instead of IDs as column names

[fivetran-jamie]

Are you a Fivetran customer?

fivetran made issue

Is your feature request related to a problem? Please describe.

not a problem per se, but a suboptimal solution to a previous problem regarding [daily issue history fields](https://github.com/fivetran/dbt_jira#daily-issue-field-history-columns). we decided to use field_ids to avoid special characters in column names in this PR https://github.com/fivetran/dbt_jira/pull/25 having columns called `customfield_[id_number]` isn't very user friendly, and i imagine users are renaming these columns as their actual field_names on top of the package models **Describe the solution you'd like** it would be great to have the columns named as their respective `field.name` instead of their ID. we can use dbt_utils.slugify() for this i think https://github.com/dbt-labs/dbt-utils/blob/main/macros/jinja_helpers/slugify.sql **Describe alternatives you've considered** - using IDs instead of potentially problematic field names **Additional context**

Please indicate the level of urgency and business impact of this request

Are you interested in contributing to this package?

• [x] Yes, I can do this and open a PR for your review.
• [ ] Possibly, but I'm not quite sure how to do this. I'd be happy to do a live coding session with someone to get this work implemented.
• [ ] No, I'd prefer if someone else did this. I don't have the time and/or don't know how to incorporate the changes necessary.

[fivetran-joemarkiewicz]

PR #54 will integrate this into the package. Thanks for the suggestion @fivetran-jamie!

[fivetran-joemarkiewicz]

The latest release of the package integrates these changes.