Fix CapioFile unlink bug and improve logging

[marcoSanti]

This pull request fixes a bug in the CapioFile class that prevented a file from being correctly removed after an unlink operation.

On the POSIX side, when a clone() was issued, the CapioFile::clone() method was invoked for each CapioFile instance registered to the calling thread (tid).

The issue was that CapioFile::clone() always incremented _n_opens. As a result, even after all threads invoked close() on the corresponding CapioFile, the internal open counter never reached zero, preventing the file from being deleted.

CapioFile::clone() no longer increments _n_opens automatically when a clone occurs. This ensures that the open counter accurately reflects the real number of active opens, allowing files to be properly removed after unlink once all handles are closed.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.14%. Comparing base (4ab957c) to head (ed58273).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #207      +/-   ##
==========================================
+ Coverage   56.13%   56.14%   +0.01%     
==========================================
  Files          71       71              
  Lines        3481     3482       +1     
  Branches     2164     2165       +1     
==========================================
+ Hits         1954     1955       +1     
  Misses        589      589              
  Partials      938      938              

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.