Azure File Mounting failures not treated as fatal even if App is not using Run-From-Package

// wawseas
FunctionsLogs
| where PreciseTimeStamp >= datetime(2023-10-11T14:08:29.803Z) and PreciseTimeStamp <= datetime(2023-10-11T14:08:44.804Z)
| where SourceNamespace == "SFLWAWS"
| where RoleInstance == "App-4E21DB8D-638326191442476902"

**Repro steps:**
Linux Consumption app
No WEBSITE_RUN_FROM_PACKAGE appsetting configured
No remote build triggered,
Configure AzureFiles using WEBSITE_CONTENTAZUREFILECONNECTIONSTRING, WEBSITE_CONTENTSHARE - BUT use invalid account credentials so mounting AzureFiles will fail at runtime.
Trigger cold start

**Expected:** Instance should cold start and be removed right away since AzureFiles mount failed and the app has no other source of app content.
**Actual:** Instance continues to stay alive with 0 functions.

**Potential Fix:**
https://github.com/Azure/azure-functions-host/blob/dev/src/WebJobs.Script.WebHost/Management/AtlasInstanceManager.cs#L310C20-L310C89
The return value from mount operation is ignored here

Start at src/WebJobs.Script.WebHost/Management/AtlasInstanceManager.cs around line 310 and trace the Azure Files mount operation used during cold start. Reproduce the Linux Consumption scenario with invalid Azure Files credentials, then verify that an app without WEBSITE_RUN_FROM_PACKAGE has its instance removed when mounting fails.

Written by the indexing model from the issue text.