[BUG] pf flow serve doesn't seem to resolve additional includes

[diftimieMSFT]

Describe the bug I have a flow that depends on code that lives in additional includes, but it looks like that code can't be found when running pf flow serve. I do not, however, run into this issue when running pf flow test or when running the flock in a built docker container.

How To Reproduce the bug Steps to reproduce the behavior, how frequent can you experience the bug (with my example):

1. Create a flow that depends on a code file with a tool implementation in a directory called shared components, not in the flow directory. in my example, I have a tool defined that lives in a file called shared_components/agent_caller.py.
2. Add this shared_components directory to the additional includes of the flow.
3. Add this tool defined in agent_caller.py to the flow.dag.yaml nodes (i.e. reference the code file)
4. Run pf flow serve --source ./orchestrator_agent/ --host localhost --port 8080

Expected behavior Flow should successfully start up

Screenshots

You can see that the captured snapshot does in fact include the code asset PF says it cannot find...

Running Information(please complete the following information):

• Promptflow Package Version using pf -v: { "promptflow": "1.16.0", "promptflow-core": "1.16.0", "promptflow-devkit": "1.16.0", "promptflow-tracing": "1.16.0" }
• Operating System: Ubuntu 18.04 on WSL2
• Python Version using python --version: python==3.11.10

Additional context Add any other context about the problem here.

[github-actions[bot]]

Hi, we're sending this friendly reminder because we haven't heard back from you in 30 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 7 days of this comment, the issue will be automatically closed. Thank you!