Standardize returning ResourceTypeSelector instances in dbt list and dbt build

[dbeatty10]

Resolves NA

Problem

There is some unnecessary code duplication as it relates to ResourceTypeSelector. The backstory is explained in the PR description for #10718.

Solution

Standardize the duplicated code.

One wrinkle to confirm

The one thing that is technically different is this line that sets include_empty_nodes=True for dbt list. The include_empty_nodes=True line was introduced in 51da375 (within #7891), presumably to resolve #7496.

There is a single case where it is false here: when test is the only selected resource. That would be an odd carve out! So I'm assuming that it is unintentional and we can safely make the change in this PR.

However, if we do want this carve out, then we should create a functional test for it, because we don't have any for it currently.

Checklist

• I have read the contributing guide and understand what's expected of me.
• I have run this code in development, and it appears to resolve the stated issue.
• Tests are not required or relevant for this PR.
• This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.).
• This PR includes type annotations for new and modified functions.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.95%. Comparing base (3e437a6) to head (092034e).
Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10739      +/-   ##
==========================================
+ Coverage   86.12%   88.95%   +2.83%     
==========================================
  Files         181      181              
  Lines       22964    22960       -4     
==========================================
+ Hits        19777    20425     +648     
+ Misses       3187     2535     -652     

Flag	Coverage Δ
integration	86.13% <100.00%> (+0.01%)	⬆️
unit	62.41% <50.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
Unit Tests	62.41% <50.00%> (∅)
Integration Tests	86.13% <100.00%> (+0.01%)	⬆️