[Tidy-First]: Fix timings object for hooks and macros, and make types of timings explicit

[aranke]

Disclaimer

test_use_custom_microbatch_strategy_env_var_true_invalid_incremental_strategy is failing across all PRs, hence the test failures

Problem

1. The timings object accepts any arbitrary keys, scope this down to just compile, execute, other`
2. hook and macro nodes should report compile and execute timings independently, but they do so combined right now.

Solution

1. Change name in timings to be a Literal
2. Use collect_timing_info instead of creating a TimingInfo object directly

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

Attention: Patch coverage is 87.09677% with 4 lines in your changes missing coverage. Please review.

Project coverage is 89.15%. Comparing base (8be0635) to head (e8ff756).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10882      +/-   ##
==========================================
- Coverage   89.20%   89.15%   -0.06%     
==========================================
  Files         183      183              
  Lines       23438    23443       +5     
==========================================
- Hits        20909    20901       -8     
- Misses       2529     2542      +13     

Flag	Coverage Δ
integration	86.43% <87.09%> (-0.13%)	⬇️
unit	62.12% <16.12%> (-0.02%)	⬇️

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

Components	Coverage Δ
Unit Tests	62.12% <16.12%> (-0.02%)	⬇️
Integration Tests	86.43% <87.09%> (-0.13%)	⬇️

[ChenyuLInx]

This change is because the new dbt-adapters change altered the behavior here

[ChenyuLInx]

LGTM

[github-actions]

The backport to 1.9.latest failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.9.latest 1.9.latest
# Navigate to the new working tree
cd .worktrees/backport-1.9.latest
# Create a new branch
git switch --create backport-10882-to-1.9.latest
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 ba6c7baf1d66d91fe7050e351e408e2a1186eee7
# Push it to GitHub
git push --set-upstream origin backport-10882-to-1.9.latest
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.9.latest

Then, create a pull request where the base branch is 1.9.latest and the compare/head branch is backport-10882-to-1.9.latest.