Log ApprovedFile access during test run (to infer orphaned files)

[MichaelRWolf]

The Sunday Mob has been working on this for a while. I don't know if it's been filed elsewhere as an issue. If so, merge the multiples.

[MichaelRWolf]

See Mermaid Online - https://www.mermaidchart.com/app/projects/aa3787ab-200f-40f6-9f3c-d864d9752ad5/diagrams/d501e5e2-a337-404c-b3e3-0fca219d964e/version/v0.1/edit

[MichaelRWolf]

Updated Sequence Diagram, showing dynamic creation of files at correct time in sequence.

[MichaelRWolf]

I now think that there are 2 branches tracking this issue:

• https://github.com/approvals/ApprovalTests.Python/tree/spike_tracking_files - On main repo. Created by @isidore, then used by that day's mob to make commits. The commits since then (via Amazon LiveStream) are NOT visible to the public (as far as I can tell).
• https://github.com/MichaelRWolf/ApprovalTests.Python/tree/log_accessed_files :: On fork of main repo. Created by me to add Mermaid file for Sequence Diagram

Proposals

• Merge both of these branches, and the invisible (but current) branch. Work only on that one separate branch.
• Practice trunk based development. Maybe yes. Maybe no. Branches are a good way to work with time-distributed and space-distributed teams working on open-source projects (EXACTLY the situation here).