Add labels to DBT models

[erikamov]

Description

This PR will add two labels to DBT models helping us to improve billing reports as part of the issue #3541.
Label were based on the current dataset structure.

• domain:

  • seeds
  • staging
  • intermediate
  • mart

• dataset:

  • audit
  • benefits (benefits and amplitude datasets)
  • gtfs (gtfs and rt datasets)
  • gtfs_quality
  • gtfs_schedule_latest
  • ntd
  • ntd_annual_reporting
  • ntd_ridership
  • ntd_safety_and_security
  • ntd_validation
  • payments
  • state_geoportal
  • transit_database
  • transit_database_latest

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

How has this been tested?

Tested locally creating tables on staging.

Post-merge follow-ups

• No action required
• Actions required (specified below)

Check if all labels on BigQuery were created after next DAGs' run.

[erikamov]

Items inside mart: (bellow) were not removed, just reordered alphabetically.

[erikamov]

ad-hoc is the only item actually removed, since there is a warning alerting about it when executing poetry run dbt run (see below) and there are no more tables on our codebase under this dataset. Looking through the logs, looks like it was just a testing dataset.

[WARNING]: Configuration paths exist in your dbt_project.yml file which do not apply to any resources.
There are 1 unused configuration paths:
- models.calitp_warehouse.mart.ad_hoc