Function instances should be disposed after call

Function instances, which contains any public methods with `[Function]` attributes, will never be disposed even they implement `IDisposable`.

### Expected behavior

Like ASP.NET Core's controllers,

* If the function instance implements `IAsyncDisposable`, its `DisposeAsync` should be called [after invocation](https://github.com/Azure/azure-functions-dotnet-worker/blob/a5fc0632d233b242debfd1485e527315567b9b3a/src/DotNetWorker.Core/Invocation/DefaultFunctionExecutor.cs#L46) even when the invocation throws.
* If the function instance implements `IDisposable`, its `Dispose` should be called after invocation even when the invocation throws.
* If the function instance implements both of `IAsyncDisposable` and `IDisposable`, `DisposeAsync` should be preferred.

### Actual behavior

Both of `IDisposable.Dispose()` and `IAsyncDisposable.DisposeAsync()` are never called.

### Runtime Information

* .NET 8
* Microsoft.Azure.Functions.Worker 1.20.0

Start by reading the linked invocation logic in src/DotNetWorker.Core/Invocation/DefaultFunctionExecutor.cs and trace how function instances are created and invoked. Confirm that async disposal is preferred, disposal occurs after both successful and throwing invocations, and instances implementing only IDisposable are also disposed.

Written by the indexing model from the issue text.