Adapt the HealthChat hooks to the upstream 26.09.1 screen APIs

The rebase onto release/26.09.1 moved three things the fork depends on.

Upstream now owns a UserProfileScreenHook of its own (#5980), which rewrites a
screen's view state rather than injecting a view. The fork's section hook keeps
its behaviour under the fork-only name ExtendedProfileSectionHook, so both can
live side by side and upstream's file stays untouched. Upstream's new @AppHook
macro generates the same register<Name> methods, so registration is unchanged.

UserProfileScreenCoordinatorParameters lost appSettings and reordered its
arguments, and UserDetailsEditScreenCoordinator now publishes its own
UserDetailsEditScreenCoordinatorAction instead of borrowing the room one
(#5893). The members flow and the profile editor follow both.

AppSettings.override gained oAuthClientURIPath (#5934), whose default appends
apps/ios to the website URL. HealthChat passes nil to keep the registered
client_uri at https://healthchat.ch exactly as the shipped build has it —
changing what the app registers with MAS is not a side effect a rebase should
have.

ElementX/Sources/AppHooks/Hooks/ExtendedProfileSectionHook.swift

@@ -9,7 +9,7 @@ import SwiftUI
 
 nonisolated protocol ExtendedProfileSectionHookProtocol: Sendable {
     @MainActor func configure(with userSession: UserSessionProtocol?) async
-
+    
     /// An extra Form section rendered below the header on the user profile
     /// and room member details screens.
     @MainActor func extendedProfileSection(userID: String) -> AnyView?
@@ -17,7 +17,7 @@ nonisolated protocol ExtendedProfileSectionHookProtocol: Sendable {
 
 struct DefaultExtendedProfileSectionHook: ExtendedProfileSectionHookProtocol {
     func configure(with userSession: UserSessionProtocol?) async { }
-
+    
     func extendedProfileSection(userID: String) -> AnyView? {
         nil
     }