Add case-insensitive collation settings to SQLite test database

[G3mha]

Describe the bug

Originated during discussion of PR #2854

SQLite test database uses case-sensitive collation while production MySQL uses case-insensitive, causing test failures for case-insensitive string operations.

To Reproduce
Steps to reproduce the behavior:

1. Go to file tests/Feature/Api/V1/UserSummaryTest.php and add the following test case:

public function testUsernameCaseConsistency(): void
{
    $user = User::factory()->create([
        'User' => 'NicoPlaysThings',
    ]);
    $variations = [
        'NICOPLAYSTHINGS',
        'nicoplaysthings',
        'NicoPlaysThings',
    ];

    foreach ($variations as $input) {
        $response = $this->get($this->apiUrl('GetUserSummary', ['u' => $input]));
        $response->assertOk()
                ->assertJsonPath('User', 'NicoPlaysThings')
                ->assertJsonPath('LastActivity.User', 'NicoPlaysThings')
                ->assertJsonPath('UserPic', '/UserPic/NicoPlaysThings.png');
    }
}

2. Run the test involving case-insensitive username lookups:

php artisan test tests/Feature/Api/V1/UserSummaryTest.php --filter testUsernameCaseConsistency

3. Observe test failure due to collation mismatch
4. See PR fix(API_GetUserSummary): handle username case sensitivity and use canonical username #2854 for the complete discussion on this error

Expected behavior

• SQLite test database should use case-insensitive collation matching MySQL's behavior
• Tests should pass regardless of username case variations
• UserSummary API tests should succeed with usernames like 'NICOPLAYSTHINGS', 'nicoplaysthings', 'NicoPlaysThings'

Additional context

• MySQL uses _ci collation by default
• SQLite test environment needs equivalent case-insensitive configuration
• Issue affects test coverage as case-sensitivity tests must be omitted
• Reference PR fix(API_GetUserSummary): handle username case sensitivity and use canonical username #2854 where this caused test coverage gaps
• Environment: PHPUnit test suite using SQLite

[wescopeland]

Thank you for opening this issue. After careful thought, I've decided to close it out.

SQLite and MariaDB are obviously different engines. If something breaks in a test as a result of those engine differences, it could hypothetically break in production too. IE: There's no guarantee we won't switch to Postgres one day.

I'm increasingly of the belief that these test failures are a feature rather than a bug. The failure is correct because it's identifying the code is implicitly relying on database-level collation instead of being explicit about what it actually wants.

When necessary, case should be handled explicitly at the query level.