Add option to disable “SELECT GET_LOCK('airflow_MIGRATIONS', 1800)“ when exec airflow db migrate

### Description

Add option to disable “SELECT GET_LOCK('airflow_MIGRATIONS', 1800)“ when exec airflow db migrate

### Use case/motivation

I deploy airflow to cloud using cloud mysql. When I exec db migrate, it throws `sqlalchemy.exc.OperationalError: (MySQLdb.OperationalError) (1105, "slice: slice-0 execution timed out, sql: SELECT GET_LOCK('airflow_MIGRATIONS', 1800)")` while my local mysql works well.
I delete the source code at airflow.utils.db.py:1364 `conn.execute(text("SELECT GET_LOCK(:id, :timeout)"), {"id": str(lock), "timeout": lock_timeout})` and airflow.utils.db.py:1379 `conn.execute(text("select RELEASE_LOCK(:id)"), {"id": str(lock)})` and exec db migrate at cloud server, all problems solved.
So, if there is a possibility that airflow could add an option using to disable sql lock check in airflow.cfg

### Related issues

_No response_

### Are you willing to submit a PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)

Start with airflow/utils/db.py around the named GET_LOCK and RELEASE_LOCK calls, then inspect how airflow db migrate reads configuration from airflow.cfg. Verify the option against the reported cloud MySQL failure; done means migrations can skip those lock queries when disabled while the current behavior remains available.

Written by the indexing model from the issue text.