Add seed table for ntd_id (2022) and (organization) source_record_id

[tiffanychu90]

Description

Try another approach at getting ntd_id_2022 added without truncating to 5 digits in every query. Add a seed table to help us bridge ntd_id_2022 with dim_organizations.source_record_id.

Follow-up to #3364
Resolves #[issue]

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?

Include commands/logs/screenshots as relevant.

Post-merge follow-ups

Document any actions that must be taken post-merge to deploy or otherwise implement the changes in this PR (for example, running a full refresh of some incremental model in dbt). If these actions will take more than a few hours after the merge or if they will be completed by someone other than the PR author, please create a dedicated follow-up issue and link it here to track resolution.

• No action required
• Actions required (specified below)

[vevetron]

I don't think we should go down this path of adding seeds for ntd_ids of data that exists in airtable already.

• In this PR Update services & organizations tables with new columns & new assessment logic #2675 they deprecated something similar to the above in favor of having the ntd_ids in airtable
• There are some duplicates in dim_org_seed_results.csvdim_org_seed_results.csvdim_org_seed_results.csv table. I'm not sure where they come from.
  A better alternative is to add the data for these columns in airtable directly.

[tiffanychu90]

@vevetron: yes, that's fine that we don't go down this path! closing this PR, but now we know how to add seed tables