fix util function to validate simple types.
fix toJSON method in last model

* chore(deps): 📦 add valibot dependency

* feat(dev): ⚗️ testing valibot in real usecase

mobile and desktop real test example.
add SyncthingSystemStatus object/schema.
valibot allows to easily parse the data coming from unknown json.

* refactor(dev): ♻️ add date schema to validate date

* feat(dev): 🐛 update date validation

update SyncthingSystemStatus to validate date types

* refactor(dev): ♻️ move date validations

* refactor(dev): ♻️ move url property to settings

* refactor(dev): ♻️ update all code to valibot

change all types used in the codebase
move to valibot schemas for easy JSON validation and typing.

* refactor(dev): 🔥 clean unused code

remove code specific to mobile

add valibot validation/parsing inside the function.
directly manage the error inside the function.
help to make it easier when calling API endpoints.
TODO: add support for more HTTP methods such as POST/PUT

update configuration view to have a msg
when syncthing needs to be restarted.
add slot in warning message.
add method param in requestEndpoint for syncthing REST datasource.

add more properties from configuration definition.
add button in settings tab to test the configuration endpoint.

create the full TS wrapper over the Syncthing API
This is the first commit for implementing every Syncthing endpoints

continue refactoring to implement all syncthing endpoints

using the new architecture/syntax.
Still need some real tests to check endpoints and syntax

update stats_device and stats_folder

update devices and folders cluster endpoints.
WIP: Still need to implement the DELETE part and test them.

all endpoints implemented

refactor all endpoints.
Still need to verify and implement some endpoints

working on folder endpoints.
still need to implement some methods for folder_versions

refactored all endpoints.
need to test them.
also need to verify syntax/validate the output

add all schemas to validate events from API calls.
will help to handle all Syncthing events.

add events entities to validate API calls
implement the endpoints
still need to validate, when I will consume the endpoint

use of svelte/stores for better reactivity

add a modal to test all the refactoring for Syncthing REST API access
this is experimental.
Will be enhanced to test all features against a Syncthing instance (created only for that)

docker compose file to create new Syncthing instances for testing purposes

change all methods to arrow functions to capture `this` in proper context.
also add a svelte component to test all the functions and methods.
will see how I check all the methods in Obsidian and if really necessary too.

update code to test some approaches for testing the syncthing remote datasource methods

add a first simple svelte component to test xstate
will be using it for more components, in particular configuration modal component

testing the xstate machines to use it for fetching configuration and updating UI.
this is for testing purposes for now

made simple xstate machine to fetch all the configuration from Syncthing instance.
for now, it fetches the config and can fail or succeed.
more features will be implemented afterwards.
a failure message is shown when there is an error occuring in the config modal.

change to npx for commitlint package

add call to syncthing system status for myID device info
also created a syncthingController machine to orchestrate all the config table fetch/update logic.