Fix generic test not null and unique custom configs

[gshank]

Resolves #

Problem

When the ability to have custom configs in generic tests was added, it missed the special code for handling not_null and unique tests.

Solution

Access "config" from the test builder instead of "get_static_config"

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.
• This PR includes tests, or 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.) or this PR has already received feedback and approval from Product or DX.
• This PR includes type annotations for new and modified functions.

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.87%. Comparing base (b414ef2) to head (79ca4a8).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #11208      +/-   ##
==========================================
- Coverage   88.93%   88.87%   -0.06%     
==========================================
  Files         187      187              
  Lines       24104    24033      -71     
==========================================
- Hits        21436    21359      -77     
- Misses       2668     2674       +6     

Flag	Coverage Δ
integration	86.17% <100.00%> (-0.15%)	⬇️
unit	62.47% <0.00%> (+0.07%)	⬆️

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

Components	Coverage Δ
Unit Tests	62.47% <0.00%> (+0.07%)	⬆️
Integration Tests	86.17% <100.00%> (-0.15%)	⬇️