Azure Functions Core Tools v4 requires AzureWebJobsStorage for "publish" command

Since Gitlab pipeline doesn't have a job for deploying Azure Function unlike Azure DevOps, I use bash scripts to deploy our Azure Function from Gitlab pipeline.

```yaml
script:
- curl -sL https://aka.ms/InstallAzureCLIDeb | bash
- wget -qO- https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > microsoft.asc.gpg
- mv microsoft.asc.gpg /etc/apt/trusted.gpg.d/
- wget -q https://packages.microsoft.com/config/debian/11/prod.list
- mv prod.list /etc/apt/sources.list.d/microsoft-prod.list
- chown root:root /etc/apt/trusted.gpg.d/microsoft.asc.gpg
- chown root:root /etc/apt/sources.list.d/microsoft-prod.list
- apt-get update && apt-get -y install --no-install-recommends azure-functions-core-tools-3
- az login --service-principal -u $APPLICATION_ID -p $APPLICATION_SECRET --tenant $TENANT_ID
- func azure functionapp publish $FUNCTION_APP --custom
```
(The entire pipeline code is [here](https://github.com/Azure-Samples/azure-function-custom-handler-with-golang/blob/main/pipelines/.gitlab-ci.yml).)

However when I change the version of azure-function-core-tools from **3** to **4**, I start to have `Error creating a Blob container reference. Please make sure your connection string in "AzureWebJobsStorage" is valid`. (azure-function-core-tools-3 works well without `AzureWebJobStorage`)

In my case, since I use this command in the pipeline I can not have local.settings.json.

This is the pipeline screenshot with azure-function-core-tools-4 (ERROR)

And this is the pipeline screenshot with azure-function-core-tools-3 (SUCCESS)

Start with the pipeline in pipelines/.gitlab-ci.yml and compare the azure-function-core-tools-3 and -4 installation and func azure functionapp publish commands. Reproduce the v4 failure in the GitLab pipeline and determine why publishing requires AzureWebJobsStorage; done means the documented publish workflow works without local.settings.json.

Written by the indexing model from the issue text.