Fix: Warn when SQLMesh automatically adjusts a restatement range to cover the whole model

[erindru]

Prior to this change, if you tried to restate eg 1 day of a model that is full_history_restatement_only, for example an INCREMENTAL_BY_UNIQUE_KEY model:

$ sqlmesh plan --restate-model sqlmesh_example.unique_key_model --start 2020-01-01 --end 2020-01-02

No changes to plan: project files match the `prod` environment

Models needing backfill:
└── sqlmesh_example.unique_key_model: [2020-01-01 - 2020-01-10]

SQLMesh would automatically adjust the backfill intervals to cover the entire model without making it obvious to the user.

Even if the user notices that the end date in this example was changed to 2020-01-10 they may be confused as to why SQLMesh ignored their specified end date of 2020-01-02.

This PR adds a warning like so:

$ sqlmesh plan --restate-model sqlmesh_example.unique_key_model --start 2020-01-01 --end 2020-01-02

[WARNING] Model 'sqlmesh_example.unique_key_model' is 'INCREMENTAL_BY_UNIQUE_KEY' which does not support partial restatement.
Expanding the requested restatement intervals from [2020-01-01 - 2020-01-02] to [2020-01-01 - 2020-01-10] in order to fully restate the model.

No changes to plan: project files match the `prod` environment

Models needing backfill:
└── sqlmesh_example.unique_key_model: [2020-01-01 - 2020-01-10]

[erindru]

The test failures are related to #3851