[12.x] Add support for native JSON/JSONB column types in SQLite Schema builder

[fuwasegu]

redo of #54984

Overview

SQLite has supported JSON data type as a built-in feature since version 3.38.0, but prior to that, users needed to opt-in by installing an extension.
Additionally, native support for JSONB type began with version 3.45.
Since Laravel 12 supports SQLite 3.26.0 and above, it should not be designed with the assumption that JSON/JSONB support is always available.
While Query\Grammars\SQLiteGrammar::class includes support for JSON functions, Schema\Grammars\SQLiteGrammar::class does not offer this option.
This PullRequest allows injecting configuration from the database connection config to enable the use of native JSON columns when defining Schema.

Details

This feature allows the following configuration in config/database.php:

'sqlite' => [
    'driver' => 'sqlite',
    'url' => env('DATABASE_URL'),
    ...,
    'use_native_json' => true,
    'use_native_jsonb' => true,
],

JSON

By setting use_native_json in a connection with sqlite driver, the following DDL changes will occur:

use_native_json = false (default)

Schema::create('sample', function (Blueprint $table) {
    $table->json('column_1');
});

create table sample
(
    column_1 text not null
);

use_native_json = true

Schema::create('sample', function (Blueprint $table) {
    $table->json('column_1');
});

create table sample
(
    column_1 json not null
);

JSONB

The same applies to JSONB:

use_native_jsonb = false (default)

Schema::create('sample', function (Blueprint $table) {
    $table->jsonb('column_1');
});

create table sample
(
    column_1 text not null
);

use_native_jsonb = true

Schema::create('sample', function (Blueprint $table) {
    $table->jsonb('column_1');
});

create table sample
(
    column_1 jsonb not null
);

[fuwasegu]

Thanks for the merge.
The schema hierarchy seems to have disappeared and use_native_json/use_native_jsonb is now placed at the top level, so I have modified the PullRequest description.