Fix: [KTOR-8881] Fix the issue with reading the configuration file.

[TuAbE]

[KTOR-8881] Determine whether the timeout is configured in application.yaml; if it is, read the configuration instead of exiting directly.(#807 OR #906)

When a timeout is defined for any LLM provider in application.yaml, use that value instead of the built-in default.

Motivation and Context

Previously the application silently ignored per-provider timeout values that were declared in application.yaml; it always fell back to the hard-coded default.

Whenever a timeout entry exists under an LLM provider in application.yaml, that value is now honoured, so operators can tune timeouts without touching code or rebuilding the artifact.

Breaking Changes

No breaking changes.

If timeout is absent from application.yaml the service behaves exactly as before (uses the built-in default).

Only users who already declared timeout but assumed it was inactive will notice the difference—those entries will now take effect, which is the intended behaviour.

---

Type of the changes

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Tests improvement
• Refactoring

Checklist

• The pull request has a description of the proposed change
• I read the Contributing Guidelines before opening the pull request
• The pull request uses develop as the base branch
• Tests for the changes have been added
• All new and existing tests passed

Additional steps for pull requests adding a new feature

• An issue describing the proposed change exists
• The pull request includes a link to the issue
• The change was discussed and approved in the issue
• Docs have been added / updated

[aozherelyeva]

Hi @TuAbE, could you please rebase the branch onto the freshest develop? I think we're good to go right after it!

[aozherelyeva]

Ah, I see, the fix is already in develop. Closing the PR then.