I like what this PR [#45] is aiming to do, but I'd ask we [@pamelafox and @spboyer] collab on a few implementation details:

• Refactor and add security scans per Refactor Azure Functions integration and enhance project structure #45
• this should use the Azure Functions Python v2 programming model, which would mean no function.json, having the right decorators, etc.
• we have a supported extension now for http streaming and fast API, as documented here. This can eliminate the whole wrapper and custom streams approach attempted currently in the sample and PR.
• this uses Consumption v1 Linux (Y1) plan which is headed towards deprecation. We should use Flex Consumption plan, MI, and optional VNET like in our other samples. Consider using 100% of the ./infra folder in this Python function http quickstart to obtain updated secure bicep for Flex.
• the dockerfile should be optional so this starts as a native Function. IFF dockerfile is requirement, then I suppose this would turn into an ACA sample. But do not try to implement this in the bicep
• the codespaces folder should xcopy this updated improved one that works with Functions: https://github.com/Azure-Samples/functions-quickstart-python-http-azd/tree/main/.devcontainer
• the readme should be updated so azure-samples metadata is not visible. you can do this by surrounding the metadata in a comment, like this: https://github.com/Azure-Samples/functions-quickstart-python-http-azd/blob/main/README.md?plain=1#L1C1-L16C4.

@spboyer and @pamelafox could we collab and merge a rev of this with the points above handled?