v0.25.23.beta1

### Fixed (This should be backported to 0.25.22 if the beta phase is prolonged)

- No longer larger files will not create a chunks during preparing `Reset Synchronisation on This Device`.

### Behaviour changes

- Setup wizard is now more `goal-oriented`. Brand-new screens are introduced.
- `Fetch everything` and `Rebuild everything` is now `Reset Synchronisation on This Device` and `Overwrite Server Data with This Device's Files`.
- Remote configuration and E2EE settings are now separated to each modal dialogue.
- Peer-to-Peer settings is also separated into its own modal dialogue.
- Setup-URI, and Report for the Issue are now not copied to clipboard automatically. Instead, there are copy dialogue and buttons to copy them explicitly.
- No longer optional features are introduced during the setup or `Reset Synchronisation on This Device`, `Overwrite Server Data with This Device's Files`.
- We cannot preform `Fetch everything` and `Rebuild everything` (Removed, so the old name) without restarting Obsidian now.

### Miscellaneous

- Setup QR Code generation is separated into a src/lib/src/API/processSetting.ts file. Please use it as a subrepository if you want to generate QR codes in your own application.
- Setup-URI is also separated into a src/lib/src/API/processSetting.ts
- Some direct access to web-APIs are now wrapped into the services layer.

### Dependency updates

- Many dependencies are updated. Please see `package.json`.
- As upgrading TypeScript, Fixed many UInt8Array<ArrayBuffer> and Uint8Array type mismatches.

src/modules/features/SetupWizard/dialogs/SetupRemote.svelte

@@ -0,0 +1,56 @@
+<script lang="ts">
+    import DialogHeader from "@/lib/src/UI/components/DialogHeader.svelte";
+    import Decision from "@/lib/src/UI/components/Decision.svelte";
+    import Question from "@/lib/src/UI/components/Question.svelte";
+    import Option from "@/lib/src/UI/components/Option.svelte";
+    import Options from "@/lib/src/UI/components/Options.svelte";
+    import Instruction from "@/lib/src/UI/components/Instruction.svelte";
+    import UserDecisions from "@/lib/src/UI/components/UserDecisions.svelte";
+        const TYPE_COUCHDB = "couchdb";
+    const TYPE_BUCKET = "bucket";
+    const TYPE_P2P = "p2p";
+    const TYPE_CANCELLED = "cancelled";
+    type ResultType = typeof TYPE_COUCHDB | typeof TYPE_BUCKET | typeof TYPE_P2P | typeof TYPE_CANCELLED;
+    type Props = {
+        setResult: (result: ResultType) => void;
+    };
+    const { setResult }: Props = $props();
+    let userType = $state<ResultType>(TYPE_CANCELLED);
+    let proceedTitle = $derived.by(() => {
+        if (userType === TYPE_COUCHDB) {
+            return "Continue to CouchDB setup";
+        } else if (userType === TYPE_BUCKET) {
+            return "Continue to S3/MinIO/R2 setup";
+        } else if (userType === TYPE_P2P) {
+            return "Continue to Peer-to-Peer only setup";
+        } else {
+            return "Please select an option to proceed";
+        }
+    });
+    const canProceed = $derived.by(() => {
+        return userType === TYPE_COUCHDB || userType === TYPE_BUCKET || userType === TYPE_P2P;
+    });
+</script>
+
+<DialogHeader title="Enter Server Information" />
+<Instruction>
+    <Question>Please select the type of server to which you are connecting.</Question>
+    <Options>
+        <Option selectedValue={TYPE_COUCHDB} title="CouchDB" bind:value={userType}>
+            This is the most suitable synchronisation method for the design. All functions are available. You must have
+            set up a CouchDB instance.
+        </Option>
+        <Option selectedValue={TYPE_BUCKET} title="S3/MinIO/R2 Object Storage" bind:value={userType}>
+            Synchronisation utilising journal files. You must have set up an S3/MinIO/R2 compatible object storage.
+        </Option>
+        <Option selectedValue={TYPE_P2P} title="Peer-to-Peer only" bind:value={userType}>
+            This is an experimental feature enabling direct synchronisation between devices. No server is required, but
+            both devices must be online at the same time for synchronisation to occur, and some features may be limited.
+            Internet connection is only required to signalling (detecting peers) and not for data transfer.
+        </Option>
+    </Options>
+</Instruction>
+<UserDecisions>
+    <Decision title={proceedTitle} important={canProceed} disabled={!canProceed} commit={() => setResult(userType)} />
+    <Decision title="No, please take me back" commit={() => setResult(TYPE_CANCELLED)} />
+</UserDecisions>