Make the sampling loop of pipelines modular, with designated inputs that can be handled iteratively with functions and a default sampler step function

### Model/Pipeline/Scheduler description

Related to #7761 .

This is an effective replacement for the existing sampling loop function and the many, many kwargs that were made to allow the user to control it or inject callbacks into it.

```py
class SamplingInput:
def __init__(self, img, text_embedding, unet, timestep=None, **kwargs):
self.img = img
self.text_embedding = text_embedding
self.unet = unet
self.timestep = timestep

# ... lots of other code ...

inp = SamplingInput(img, text_embedding, unet)
with self.progress_bar(total=num_inference_steps) as progress_bar:
for i, t in enumerate(timesteps):
inp.timestep = t
for sampling_function in self.sampling_functions:
inp = sampling_function(inp)

output_img = inp.img
```

This will give the end user complete control of the sampling loop, allow the repo to add "official inline sampling functions" like report an image to an endpoint so that the user can view intermediate steps, etc.

We can add an argument sampling_functions: `list[Callable]=[default_sampling_function]` into the `__call__` as a new, backwards compatible kwarg.

This requires a rewrite of all of the pipelines, but as it is a backwards compatible change it can be introduced to any of the more popular pipelines first.

パイプライン内の既存の sampling ループとその __call__ エントリポイントを確認し、sampling 関連の kwargs とコールバックがどのように処理されているかを比較します。提案された例に基づいて、SamplingInput、sampling_functions、default_sampling_function のインターフェースを定義します。モジュール化されたループが互換性を保って導入され、影響を受ける主要なパイプラインが既存の動作を変更せずに更新されれば完了です。

索引モデルが issue の本文から書いたものです。