Sort nodes in graph object by memory impact when building subdag

[ttusing]

Partially resolves #7195

Description

This implements the node sorting suggested in #7195. This is contained partially in #7194 and a separate PR is opened here in case the other changes in #7194 are not ready to be reviewed. This also includes a performance check for this change alone with the other new performance enhancements merged into the 1.5 beta (#7191).

Performance tests:

Current 1.5 beta:

dbt=1.5.0-b5
(env)  % dbt build --no-version-check -s mymodel
19:05:38  Running with dbt=1.5.0-b5
19:05:41  Found 306 models, 3346 tests... 
19:06:10  
19:06:16  
19:06:16  Running 1 on-run-start hook
19:06:16  1 of 1 START hook: on-run-start.0 ...................................... [RUN]

48 seconds

This branch:

(env)  % dbt build --no-version-check -s mymodel
19:03:39  Running with dbt=1.5.0-b5
19:03:42  Found 306 models, 3346 tests...
19:03:42  
19:03:48  
19:03:48  Running 1 on-run-start hook
19:03:48  1 of 1 START hook: on-run-start.0 ...................................... [RUN]

9 seconds

Because of the huge performance gains, I believe many teams would benefit from getting this change into DBT as soon as possible.

Checklist

• [XX] I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

[ttusing]

@iknox-fa @peterallenwebb I spun out this PR in case some of the changes in #7194 require more in-depth review. I also re-ran performance checks, this sorting change alone improves at least my DBT project for developing a single model by 5x compared to 1.5.0-b5 and it seems highly unlikely to have any unintended impacts.

[ttusing]

Closing since #7194 was merged