Functions V4 .NET 6 - Errors on Sync Web Apps Function Triggers/functions disappear from list

I am trying to deploy a brand new Functions app using v4 and on .NET 6. This is a class library project that publishes multiple dlls. I have 4 ServiceBusTriggers, and can run & debug functions locally. There are no warnings nor errors in the local func.exe execution.

I can navigate to the host logs via the kudu debug console and find logs that match my local development experience. Startup is successful, as well as execution.

The problem comes in when I want to view/monitor my functions. After a successful deployment, the functions initially show in the list, but an `Azure Functions runtime is unreachable` message is shown at the top. After some time interval, the functions list clears out.

When trying to view the log stream, I'm shown an error that says
> Unable to fetch the host status of your function app. To use log streaming, please make sure your function host is running.

The function apps activity log shows failures for both
- List Web Apps Functions Host Keys
- Sync Web Apps Function Triggers

These errors have presented themselves on both consumption plan + ASP hosting options.

A valid AzureWebJobsStorage connection string is set on the configuration of the function app.

#### Investigative information

Please provide the following:

- Timestamp: `Wed Jun 29 2022 16:12:07 GMT-0500 (Central Daylight Time)`
- Function App version: `V4`
- Function App name: `seismic3-dev-functions`
- Function name(s) (as appropriate):
--`NotificationProcessorEmail` serviceBusTrigger
--`NotificationProcessorHost` serviceBusTrigger
--`NotificationProcessorPush` serviceBusTrigger
--`NotificationProcessorSms` serviceBusTrigger
- Invocation ID:
- Region: `East US`

#### Repro steps

Provide the steps required to reproduce the problem:

Deploy the function app. Initially the functions will display in the list, but disappear after some interval.

I have deployed via Azure DevOps as well as the built in Visual Studio 2019 tooling to deploy the app. Both end up with the same behavior.

#### Expected behavior

Provide a description of the expected behavior.

Functions do not disappear.

#### Known workarounds

Provide a description of any known workarounds.

None.

Start with the Azure Functions v4 .NET 6 deployment and host logs available through the Kudu debug console, then compare them with local func.exe output. Investigate the failures for “List Web Apps Functions Host Keys” and “Sync Web Apps Function Triggers” across the reported hosting plans. Done means the deployed ServiceBusTrigger functions remain listed and log streaming and host-status requests succeed.

Written by the indexing model from the issue text.