Include original file name/path in bndb metadata created under projects

What is the feature you'd like to have?
Original file path/name to be included in metadata for a bndb under a project, something like bv.file.project_file.original_name or something discerning between the uuid project names and the file path of the binary being analyzed

Is your feature request related to a problem?
Plugins will reference the original path to the binary being worked on via bv.file.original_name, this functionality completely breaks when operating within a project.

bncov for example will fail to run when operating within a project becuase of this:
https://github.com/ForAllSecure/bncov/blob/master/coverage.py#L26

Are any alternative solutions acceptable?
N/A

Additional Information:
For example, in a binja-test-proj project, if you were to import /tmp/test.so then start reversing and save the bndb, you would end up with a test.bndb, you can use bv.file.project_file.name to get test.bndb. There is currently no way from the bndb to obtain the path of the original binary being analyzed at /tmp/test.so

Start with the project-file metadata exposed through bv.file.project_file.name and compare it with bv.file.original_name; the issue's bncov coverage.py example shows the broken consumer. Trace how a project-created bndb stores and exposes metadata. Done means a project bndb provides the original binary path or name distinctly from its UUID-based project file name.