Instead of throwing a RuntimeError if a Component has not been warmed up just call `warm_up` at runtime

[sjrl]

With recent PRs introducing new warm up methods to Tools, Toolsets (#9856), ChatGenerators (#9942) and Agents I think it's worth revisiting our design choice to raise an error when running an not warmed up component when using it standalone.

This is already a non-issue when using components in a pipeline since the pipeline will always call warm_up on it's member components at runtime. I think this is a better developer experience (to auto call warm_up at runtime) rather than make users have to explicitly call it when using components like Agent standalone.

This would also prevent recent PRs like #9942 and #9965 from being breaking changes when used in certain scenarios (e.g. using an OpenAIChatGenerator inside an Agent component without calling Agent.warm_up now throws an error).

[anakin87]

I understand the motivation, but I also realize that this would be a significant change across the framework.

For the time being, do you think we could simply make a similar change to prevent the PRs mentioned to be breaking?

[sjrl]

I understand the motivation, but I also realize that this would be a significant change across the framework.

For the time being, do you think we could simply make a similar change to prevent the PRs mentioned to be breaking?

I'm not really sure how we'd prevent them from being breaking other than updating Agent and LLMMessagesRouter to auto warm_up at runtime instead of throwing an error.

[anakin87]

I'm not really sure how we'd prevent them from being breaking other than updating Agent and LLMMessagesRouter to auto warm_up at runtime instead of throwing an error.

Yes, I was suggesting something like this but only for these components at the moment.

(I think that adopting this idea across all framework needs some design effort.)

[sjrl]

Re-opening to track making this change across the code base. The PR #9987 only updated components that take in a ChatGenerator as input.