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

[Tigrov]

Optimization

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

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

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

Additional details and impacted files

```diff @@ 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 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[what-the-diff[bot]]

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.