Feature: Signals print if triggered vs. not during runs

[sungchun12]

In the CLI output, signals work by matter of seeing the model run or not. For debugging and development, it should have a default option to print a message that it triggered and which model(s) it's triggering.

It follows the spirit of #4113

[sungchun12]

Mockup of when it runs on a plan.

Updating physical layer ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100.0% • 4/4 • 0:00:00

✔ Physical layer updated

Checking signals status before executing model batches:
  sushi.model_with_signals
  ├── [1/2] only_first_two_in_batch_ready  0.01s
  │   ├── check: 2023-01-01 - 2025-06-18
  │   └── ready: 2023-01-01 - 2023-01-02 # color code yellow for partial ready intervals
  │   └── note: Whatever message you want to show here if configured by user. ex: upstream   
  │         data only shows 2 days are ready. Wrap the text in terminal or make newlines.
  └── [2/2] another_test_signal            0.01s
      ├── check: 2023-01-01 - 2023-01-02
      └── ready: 2023-01-01 - 2023-01-02 # color code green for all intervals ready
  sqlmesh_example.incremental_model
  └── [1/1] only_first_two_in_batch_ready  0.01s
      ├── check: 2020-01-01 - 2025-06-18
      └── ready: no intervals # color code red
  sqlmesh_example.full_model
  └── [1/1] only_first_two_in_batch_ready  0.01s
      ├── check: TRUE or FALSE
      └── ready: FALSE # color code red, green if TRUE

[1/1] sqlmesh_example.seed_model          [insert seed file]                 0.00s
[1/1] sushi.model_with_signals            [insert 2023-01-01 - 2023-01-02]   0.01s
[1/1] sqlmesh_example.incremental_model   [insert 2020-01-01 - 2020-01-02]   0.01s
[1/1] sqlmesh_example.full_model          [skip-signals not ready]           0.00s
Executing model batches ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100.0% • 3/3 • 0:00:00

✔ Model batches executed

Updating virtual layer  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100.0% • 3/3 • 0:00:00

✔ Virtual layer updated