Add dbt_tld for maintenance of top level domain lookup table

[GJMcClintock]

Description

This is a simple package that maintains a seed file of the currently accepted IANA TLDs.

Link to your package's repository: https://github.com/GJMcClintock/dbt_tld/tree/0.1.0

Checklist

This checklist is a cut down version of the best practices that we have identified as the package hub has grown. Although meeting these checklist items is not a prerequisite to being added to the Hub, we have found that packages which don't conform provide a worse user experience.

First run experience

• [x] The package includes a README which explains how to get started with the package and customise its behaviour
• [x] The README indicates which data warehouses/platforms are expected to work with this package

Customisability

• [x] The package uses ref or source, instead of hard-coding table references.

Dependencies

Dependencies on dbt Core

• [x] The package has set a supported require-dbt-version range in dbt_project.yml. Example: A package which depends on functionality added in dbt Core 1.2 should set its require-dbt-version property to [">=1.2.0", "<2.0.0"].

  Interoperability

• [x] The package does not override dbt Core behaviour in such a way as to impact other dbt resources (models, tests, etc) not provided by the package.
• [x] The package uses the cross-database macros built into dbt Core where available, such as {{ dbt.except() }} and {{ dbt.type_string() }}.
• [x] The package disambiguates its resource names to avoid clashes with nodes that are likely to already exist in a project. For example, packages should not provide a model simply called users.

Versioning

• [x] (Required): The package's git tags validates against the regex defined in version.py
• [x] The package's version follows the guidance of Semantic Versioning 2.0.0. (Note in particular the recommendation for production-ready packages to be version 1.0.0 or above)

[joellabes]

Hey @GJMcClintock, this is very cool! One comment: instead of calling split_part directly, you should use the cross-db implementation defined here, i.e. {{ dbt.split_part() }}. This will ensure that any warehouses that use a different syntax are also compatible.

That can be handled in a different release though, so I'll merge this!

[GJMcClintock]

@joellabes - I just released a patch to switch to the cord split_part - I didn't realize that was a function. Thanks for the heads up!