Template Gallery and classic flow initialize different default values for AzureWebJobsStorage

[v-ruizh]

OS: Win 11 x64
Build Version: 20260602.6

Repro Steps:

1. Create a new Azure Functions project using Template Gallery.
2. Open local.settings.json file.
3. Observe: "AzureWebJobsStorage": "UseDevelopmentStorage=true"
4. Create another Azure Functions project using the classic flow.
5. Open local.settings.json file.
6. Observe: "AzureWebJobsStorage": ""

Expect:
Project initialization behavior should be consistent across creation flows.

Actual:
Template Gallery initializes AzureWebJobsStorage to use the emulator (UseDevelopmentStorage=true).
Classic flow initializes AzureWebJobsStorage as empty.

[gavin-aguiar]

The "AzureWebJobsStorage": "UseDevelopmentStorage=true" is coming existing Function App samples and it's the right way to initialize local settings. Maybe we can change the classic flow to this same setting

[nturinski]

Yeah, there's definitely a case that could be made to set this to use the emulator by default for the classic flow. We originally didn't because Azurite wasn't a widely available emulator at that time, but since it's easy enough for any user to install, we should probably just direct them to use the emulator.