[12.x] Added MySQL DDL locking options to MySQL grammar

[Vladelis]

Problem

Right now when writing MySQL DDL Operations in migrations it is not possible to define what locking mechanism to use for the statement.

This makes it possible to define what locks to use for altering tables.

Usage example:

    Schema::table('students', function (Blueprint $table) {
        $table->index('email')->lock('none');
    });

As opposed to previously needing something like this

    if (DB::getDriverName() === 'mysql') {
          DB::statement('
              ALTER TABLE `students`
              ADD INDEX `students_email_index` (`email`),
              LOCK = NONE
          ');
    } else {
          Schema::table('students', function (Blueprint $table) {
              $table->index('email');
          });
    }

[github-actions]

Thanks for submitting a PR!

Note that draft PR's are not reviewed. If you would like a review, please mark your pull request as ready for review in the GitHub user interface.

Pull requests that are abandoned in draft may be closed due to inactivity.

[AidasK]

Would love to have, most of my migrations are using this.