MisconfigurationException use cases

Nobody has claimed this yet.

### Outline & Motivation

```
if (
self.trainer.max_epochs != -1
and self.trainer.max_epochs is not None
and self.trainer.current_epoch > self.trainer.max_epochs
):
raise MisconfigurationException(
f"You restored a checkpoint with current_epoch={self.trainer.current_epoch},"
f" but you have set Trainer(max_epochs={self.trainer.max_epochs})."
)```

### Pitch

```
if (
self.trainer.max_epochs != -1
and self.trainer.max_epochs is not None
and self.trainer.current_epoch > self.trainer.max_epochs
):
return None
```

### Additional context

_No response_

cc @lantiga @justusschock

Start with the checkpoint-restoration logic that compares Trainer.current_epoch with Trainer(max_epochs), then trace how MisconfigurationException is surfaced. Done means the agreed behavior for this mismatch is implemented, including the proposed return of None instead of raising the exception.

Written by the indexing model from the issue text.