Do not log dark storage info to terminal

[larsevj]

Issue
Resolves #9707

Should hopefully not interfere with the propagation of dark storage logs to azure.

• PR title captures the intent of the changes, and is fitting for release notes.
• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.
• Make sure unit tests pass locally after every commit (git rebase -i main --exec 'pytest tests/ert/unit_tests -n auto --hypothesis-profile=fast -m "not integration_test"')

When applicable

• When there are user facing changes: Updated documentation
• New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
• Large PR: Prepare changes in small commits for more convenient review
• Bug fix: Add regression test for the bug
• Bug fix: Create Backport PR to latest release

[codspeed-hq]

CodSpeed Performance Report

Merging #9815 will not alter performance

_{Comparing larsevj:remove_openapi_logs_from_terminal (2666cb7) with main (fd06848)}

Summary

✅ 24 untouched benchmarks

[HakonSohoel]

💯

I've verified that dark storage logs are still propagated to azure