Fix call to LLM logger breaking scan

[mattbit]

For scans that do not require the LLM client (special char injections, etc.), the scanner must not break if the LLM client is not set.

[sentry]

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: giskard/scanner/scanner.py

Function	Unhandled Issue
analyze	OpenAIError: The api_key client option must be set either by passing api_key to the client or by setting the O... ... Event Count: 3
analyze	ModuleNotFoundError: No module named 'langchain.chains.LLMChain' __ma... Event Count: 1
analyze	RuntimeError: No issue detectors available. Scan will not be performed. ... Event Count: 1
analyze	LLMImportError: It seems that you are using Giskard LLM functionality but you are missing some required package. ... ... Event Count: 1

---

_{Did you find this useful? React with a 👍 or 👎}

[andreybavt]

you can remove this line, the llm_logger will already contain this value

Change has been applied

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud