write a log record when tree import succeeded or failed

[BertKoor]

this fixes issue #5379

[codecov]

Codecov Report

❌ Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 35.77%. Comparing base (a64cc99) to head (3b3b9cd).
⚠️ Report is 57 commits behind head on main.

Files with missing lines	Patch %	Lines
app/Http/RequestHandlers/GedcomLoad.php	0.00%	3 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #5407      +/-   ##
============================================
+ Coverage     35.49%   35.77%   +0.27%     
+ Complexity    11211    11206       -5     
============================================
  Files          1166     1181      +15     
  Lines         48077    48026      -51     
============================================
+ Hits          17065    17180     +115     
+ Misses        31012    30846     -166     

☔ View full report in Codecov by Harness.
📢 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ddrury]

Wouldn't the edit log be a better bet than the config log

[BertKoor]

Wouldn't the edit log be a better bet than the config log

Good question! My consideration to determine which to use, is that an editor cannot do an import. It can only be done by an administrator via the control panel. And thus the config section is imho a better fit.

I did change the log records written when an import fails to the error type.