Web support for the Website service (#17)

This PR contains the work done to introduce a new Web Swift package that provides a reusable, declarative way to register route controllers on a Hummingbird router, then adopt it in the Website service.

To provide further details about the work:

* Web package
  * The `RouterController` protocol — a Sendable protocol to group controllers behind one `routes` property.
  * The `RouteCollectionBuilder`  — a result builder that collects controllers' route collections into a stack, with full support for optionals, conditionals, and arrays.
  * The `addController(_:)` method — a `RouterMethods` extension letting controllers be listed declaratively and adding each one's routes at the router root.

* Website service
  * Added Web as a dependency of the _WebsiteLibrary_ target.
  * Conformed the `RootController` and `HealthController`controllers to the `RouterController` protocol.
  * Updated the `App+Build` extension to to use the cleaner `router.addController { … }` instead.

Reviewed-on: rock-n-code/loud-amsterdam#17
Co-authored-by: Javier Cicchelli <javier@rock-n-code.com>
Co-committed-by: Javier Cicchelli <javier@rock-n-code.com>

Services/Website/Sources/Library/Public/Controllers/HealthController.swift

@@ -1,13 +1,16 @@
 import Hummingbird
 import NIOCore
 import Persistence
+import Web
 
 /// Serves the website's health-check routes.
 ///
-/// The controller exposes its routes as a `RouteCollection` so they can be added to a router (or a sub-group) by the application that composes it:
+/// The controller exposes its routes through its `RouterController` conformance, so the application that composes it registers them declaratively:
 ///
 /// ```swift
-/// router.addRoutes(HealthController<AppRequestContext>(probe: probe).routes)
+/// router.addController {
+///     HealthController<AppRequestContext>(probe: probe)
+/// }
 /// ```
 ///
 /// It always serves a liveness check at `/health`; when a `Probe` is supplied it also serves a readiness check at `/health/ready` that reports
@@ -15,7 +18,7 @@ import Persistence
 /// readiness failure.
 ///
 /// - Note: `Context` is the request context the routes are resolved against, and must match the context of the router the routes are added to.
-public struct HealthController<Context: RequestContext>: Sendable {
+public struct HealthController<Context: RequestContext> {
 
     // MARK: Properties
 
@@ -33,13 +36,14 @@ public struct HealthController<Context: RequestContext>: Sendable {
         self.probe = probe
     }
 
-    // MARK: Computed
+}
+
+// MARK: - RouterController
+
+extension HealthController: RouterController {
+
+    // MARK: Properties
 
-    /// The routes served by the controller.
-    ///
-    /// Serves a `GET` request for the liveness path (`/health`) with a static JSON status payload, and —
-    /// when a `Probe` was supplied — a `GET` request for the readiness path (`/health/ready`)
-    /// that consults the probe.
     public var routes: RouteCollection<Context> {
         let routes = RouteCollection(context: Context.self)