Checking if a file belongs in --traversal does not account for relative paths.

[teo-tsirpanis]

Repro (the same I had sent on Discord)

The file tiledb\api\c_api\vfs\vfs_api_external.h has an #include "..\context\context_api_external.h" in it. All header files in the tiledb directory are passed to the tool via --traverse, but the tool sees the path tiledb\api\c_api\vfs\..\context\context_api_external.h, does not resolve the relative path and does not find it in the list, and skips context_api_external.h.

[tannergooding]

This should likely be a relatively easy fix.

I imagine we just need to extend IsIncludedFileOrLocation to also check _config.TraversalNames.Contains(Path.GetFullPath(...))

or alternatively to have PInvokeGeneratorConfiguration implicitly add the full path as an alternative to the set.

The latter is a bit more up-front cost but is overall more extensible and could be handled as part of the AddRange in the property init

[teo-tsirpanis]

Thanks for fixing it!