[SQL] Optional migrations applying

### Describe the problem

Currently, the client side `load()` runs migrations in a "forced" way. There is no way to skip the process.
I think there are cases where the feature can be useful:
- The original migration script is lost and checksum is wrong. In this case there is no way to establish the connection with the database to fix the migrations table.
- Changing from inline SQL in the migrations to a separate .sql files.
- Fix SQL formatting in the migrations.
- Skip migrations applying if you know they are applied.

### Describe the solution you'd like

A solution could be a bool parameter for `load()` method:
```ts
import Database from '@tauri-apps/plugin-sql';
const db = await Database.load('sqlite:mydatabase.db', false);
```
parameter name: `applyMigrations`
default value: `true`

### Alternatives considered

Also can be added to the plugin builder:
```rs
.plugin(
tauri_plugin_sql::Builder::new()
.add_migrations(
config
.get_string("database.connection-string")
.expect("'database.connection-string' not found in config")
.as_str(),
migrations::migrations(),
)
.applyMigrations(false) // <-- new feature
.build(),
)
```

### Additional context

_No response_

Start with the client-side `load()` API and the Rust plugin builder path using `add_migrations()` described in the issue. Trace where migrations are currently forced, then determine how the default behavior and an opt-out configuration should work; done means callers can skip migration application while existing callers still apply migrations by default.

Written by the indexing model from the issue text.