Add FIBContext logic to handle manual mode AutoTEM data

[tieneupin]

The FIBContext was previously written to handle data structures produced by an automated AutoTEM session, and would trigger incorrectly when encountering manual AutoTEM datasets. In this PR, we have added additional checks to incoming files in the FIBContext to allow it to work with both manual and automated AutoTEM projects:

• The FIBContext will now note down the file path and project folder name of all ProjectData.dat files observed
• When a file with a relevant path pattern is detected, it will mark the project folder the file belongs to as the project folder to be analysed.
  • Automated AutoTEM projects will have folders named "Lamella ..."
  • For manual AutoTEM projects, we look for the project folder containing "DCImages" and "LamellaEvaluationImages"
• Once the target project folder has been identified, it will belatedly process the ProjectData.dat file for that project and trigger processing on any files from that folder as normal.

[codecov]

Codecov Report

❌ Patch coverage is 94.11765% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 53.39%. Comparing base (975c2f3) to head (1ff5660).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #836      +/-   ##
==========================================
+ Coverage   53.31%   53.39%   +0.08%     
==========================================
  Files         101      101              
  Lines       10933    10935       +2     
  Branches     1452     1454       +2     
==========================================
+ Hits         5829     5839      +10     
+ Misses       4788     4784       -4     
+ Partials      316      312       -4     

🚀 New features to boost your workflow:

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