Automatically convert non-flows into flows

[jakekaplan]

This PR updates load_flow_from_entrypoint to automatically wrap any Python function in a Flow object if it is not already, removing the requirement that a user explicitly decorate their function with @flow if they want to deploy it. By doing so, we lower the barrier for using Prefect to remotely deploy and run code—allowing quick adoption without forcing users to modify existing codebases as existing scripts become immediately deployable/schedulable.

As far I can tell there is no technical reason why we can't do this and I think it is a very big value add. I would be happy only include this functionality behind an experimental flag if that is preferred.

[codspeed-hq]

CodSpeed Performance Report

Merging #17024 will not alter performance

_{Comparing all-flow-everything (c266704) with main (332413a)}

Summary

✅ 2 untouched benchmarks

[desertaxle]

My initial reaction is that this is cool and should be its own utility. That way we can keep the behavior of the current utility consistent and sidestep any edge cases that might arise if we get a ScriptError while loading a function that isn't already decorated with @flow.

[jakekaplan]

My initial reaction is that this is cool and should be its own utility. That way we can keep the behavior of the current utility consistent and sidestep any edge cases that might arise if we get a ScriptError while loading a function that isn't already decorated with @flow.

That sounds good to me! I made a tweak here (still need to fix tests). Is this what you had in mind? Or is there a different way/different place you'd recommend?

[zzstoatzz]

cool!