Changelog category (leave one):

• Not for changelog (changelog entry is not required)

Logging exceptions in destructor of static objects can access freed objects because we don't know in which order are the objects destroyed (e.g. StackTraceCache we use for generating stacktraces).
To prevent this I added couple of safeguards where:

• logging is disabled after BaseDaemon object is destroyed
• StackTrace doesn't use cache if the cache object is destroyed

I also noticed that we don't handle exceptions for LazyPipeFDs::close correctly in some places so I added a failpoint and a test.

Fix #67001

Documentation entry for user-facing changes

• Documentation is written (mandatory for new features)

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

CI Settings (Only check the boxes if you know what you are doing):

• Allow: All Required Checks
• Allow: Stateless tests
• Allow: Stateful tests
• Allow: Integration Tests
• Allow: Performance tests
• Allow: All Builds
• Allow: batch 1, 2 for multi-batch jobs
• Allow: batch 3, 4, 5, 6 for multi-batch jobs

• Exclude: Style check
• Exclude: Fast test
• Exclude: All with ASAN
• Exclude: All with TSAN, MSAN, UBSAN, Coverage
• Exclude: All with aarch64, release, debug

• Do not test
• Woolen Wolfdog
• Upload binaries for special builds
• Disable merge-commit
• Disable CI cache