-D relativeDump, option to remove personal path data from hxb-dump

Currently hxb-dump exports personal path data ( relative ) rather than absolute.

Problems:
Personal information about your computers file structure, making it not suitable/ideal to share hxb files on repos.
Bloating the cross data, and can add complexity to process data.

Why it maybe relevant.. in theory it is possible to apply Linear Flow Lifetime Analysis to hxb files, making it easier to target unmanaged languages. For reference Lobster does this ( think easy rust, but with an ecosystem that is even less easy for getting a job than haxe cool languages are rarely mainstream ) and Roc, and Julia may provide some dynamic insight and perhaps lobster and roc can provide real test cases to reduce managed code. But effectively hxb is a binary AST format by nature due to haxe's language flexiblity - it is perhaps ideal to assist with transpiler conversion, but not having an option to omit personal file paths from the hxb-dump seems a shame. While it maybe super important for hxb design use, to speed up the compiler, it seems not ideal for hxb reuse beyond. I have asked AI but it has failed so far despite macros beyond me. Been playing with haxe and go but injecting 'crL' data is not for me easy. Anyway absolute paths in hxb seem to be a kind of mistake... perhaps just in one special hxb one?

Start by locating the hxb-dump entry point and the code that writes path data into hxb files. Check whether existing tests cover dump output; done means an option can remove personal path data while preserving usable hxb output.

Written by the indexing model from the issue text.