Determine usability of WebAPI

[stijnmoreels]

During the slimmed-down exercise, it came to our attention that lots of Arcus functionality should be reviewed in terms of usability, in favor of using new built-in Microsoft supported functionality. This discussion item showcases what current functionality should either be removed or changed.

• ❌ Remove Arcus.WebApi.Hosting.AzureFunctions package, as this package is only used for Azure Functions - which we stop supporting directly in other Arcus repo's. The only functionality here is that it can restrict isolated HTTP functions to only use JSON request/response, which by itself is a rather project-specific setup that would possibly require customization of error messages and/or a range of 'accepted' content types. The added-value of this package is therefore rather minimal and only usable in very specific circumstances.
• ❌ Remove Arcus.WebApi.Logging.AzureFunctions package, as this package only has two middleware components (exception handling + request tracking). The exception handling is a very small component, that needs possibly be configured specifically for each project, which makes it a rather un-Arcus thing. The request tracking middleware component builds on the Arcus.Observability Serilog setup, which is also being reviewed and possibly removed. Also: Azure Functions is being stopped supporting built-in for Arcus.
• ❌ Remove Arcus.WebApi.Logging package, as this mostely provides correlation formats that are either deprecated (Hierarchical) or built-in supported by OpenTelemetry (W3C) in ASP.NET Core applications (https://learn.microsoft.com/en-us/dotnet/core/diagnostics/observability-with-otel)
• ❌ Remove the direct link with Arcus.Security in the Arcus.WebApi.Security, so that both packages can continue being developed separately.
  • The functionality of this package should also be reviewed. We currently have SharedAccessKey, Certificate and JWT as authentication systems, which some of them might already be suppored by Microsoft, now.
  • This has also impact on the .OpenApi.Extensions package, that provides OpenAPI documentation for the authentiation filters.
• ❌ Remove the Arcus.WebApi.Hosting package, as it only has a single extension there to only allow JSON formatting in API applications - which is too project specific.

[stijnmoreels]

Wondering if this entire repository should be archived, even.