[FEATURE]: Add a way to mark migrations as applied

### Feature hasn't been suggested before.

- [x] I have verified this feature I'm about to request hasn't been suggested before.

### Describe the enhancement you want to request

It would be useful if Drizzle Kit had a first-class command to mark a migration as already applied without executing it.

For example:

drizzle-kit migrate --mark-applied 0005_add_users

or perhaps:

drizzle-kit mark-applied 0005_add_users

The use case is when a migration has already been applied manually (or by another deployment mechanism), but Drizzle's migration journal doesn't know about it.

Currently, the workaround is to manually modify the Drizzle migrations table, which is error-prone and requires knowing the exact format/hash expected by the current Drizzle Kit version.

A built-in command could:

Verify that the migration exists locally
Calculate/verify its expected hash
Insert the appropriate record into the migrations table
Never execute the migration SQL
This would be especially useful for production databases where a migration has already been applied outside of Drizzle, or when adopting Drizzle on an existing migration history.

It would be great to have a safe, officially supported way to do this.

Start by reviewing Drizzle Kit's existing migrate command and migrations-table handling. Define how a mark-applied command should verify a local migration and its hash, record it without executing migration SQL, and support manually applied histories. Done means the behavior is safe and officially supported for production and existing migration histories.

Written by the indexing model from the issue text.