Do not call CommandInterface::getRawSql() if no logger or profiler

[Tigrov]

Optimization

Q	A
Is bugfix?	❌
New feature?	❌
Breaks BC?	❌
Fixed issues	-

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (c4c4a9d) 99.64% compared to head (dbdc094) 99.64%.

Additional details and impacted files

@@            Coverage Diff            @@
##             master     #781   +/-   ##
=========================================
  Coverage     99.64%   99.64%           
- Complexity     1264     1265    +1     
=========================================
  Files            63       63           
  Lines          3062     3063    +1     
=========================================
+ Hits           3051     3052    +1     
  Misses           11       11           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[what-the-diff]

PR Summary

• Introduction of new entry in CHANGELOG
  A new record has been added to the history of modifications made in our codebase (CHANGELOG.md). This record indicates a change we made that improves efficiency by avoiding unnecessary operations when there's no need to log or profile the running process.

• Optimization in AbstractPdoCommand
  We revamped the part of our code (AbstractPdoCommand.php) that deals with database operations. Now, it will log the executed database query only when a logger is available. Similarly, it will profile (measure the performance of) the process if and only if a tool for doing that is set up. This speeds up our code when these kinds of diagnostic settings are not in place.

[vjik]

If add result caching to getRawSql() method, then we can reafactor code so:

$this->profiler?->begin($this->getRawSql(), $queryContext);

If profile is null then $this->getRawSql() don't call.