feat: add a conversationId as an info log to ease customer feedback

[sannicm]

Problem

Searching for the conversationId in logs could be cumbersome for some customers. This aims to make it a little bit easier.

Solution

Add an info level log with the conversation id in approach and code generation, including their iterations for easy conversation Id finding.

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[jsalles]

Can we also add this log message after we receive the conversationId from StartConversation?
That way we'll have this info for flows that fail before starting planning.

[sannicm]

Can we also add this log message after we receive the conversationId from StartConversation? That way we'll have this info for flows that fail before starting planning

Printing effectively after the preloader runs is doing what you suggest, printing before any approach interaction is done. This way we would have conversationId in every approach plan or plan iteration as well before any upload or generation.