Feature: Add transaction_accounting_lines_pass_through_columns support #207

Summary

The package supports pass-through columns for transactions, transaction_lines, accounts, customers, departments, locations, subsidiaries, vendors, items, classes, consolidated_exchange_rates, nexuses, entities, and accounting_periods — but not for transaction_accounting_lines.

Current behavior

stg_netsuite2__transaction_accounting_lines_tmp pulls all columns from the raw source (including paymentamountunused and paymentamountused), but stg_netsuite2__transaction_accounting_lines uses an explicit column list in the final CTE that drops them. There is no transaction_accounting_lines_pass_through_columns variable, no fivetran_utils.add_pass_through_columns call in get_netsuite2_transactionaccountingline_columns(), and no fill_pass_through_columns call in the staging model.

Requested behavior

Add transaction_accounting_lines_pass_through_columns support matching the existing pattern used by transaction_lines:

1. Add transaction_accounting_lines_pass_through_columns: [] default var in dbt_project.yml
2. Add {{ fivetran_utils.add_pass_through_columns(columns, var('transaction_accounting_lines_pass_through_columns')) }} to get_netsuite2_transactionaccountingline_columns()
3. Add {{ netsuite.fill_pass_through_columns(var('transaction_accounting_lines_pass_through_columns', [])) }} to the final select in stg_netsuite2__transaction_accounting_lines.sql

Use case

Payment reporting requires paymentamountunused and paymentamountused per accounting book (for multibook environments). Without pass-through support, consumers must bypass the package staging layer and read the raw source directly, breaking the layered architecture the package provides.

Package version

v1.6.0