### Description

It would be nice if we could give the DatabricksSubmitRunOperator a pipeline name instead of a pipeline_id for cases when you do not already know the pipeline_id but do know the name. I'm not sure if there's an easy way to fetch a pipeline_id.

### Use case/motivation

Avoid hardcoding pipeline ID's, storing the ID's elsewhere, or fetching the pipeline list and filtering it manually if the pipeline name is known, but ID is not.

### Related issues

_No response_

### Are you willing to submit a PR?

- [X] 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)

exception_message = "Argument 'job_name' is not allowed with argument 'job_id'"
        with pytest.raises(AirflowException, match=exception_message):
            DatabricksRunNowOperator(task_id=TASK_ID, job_id=JOB_ID, job_name=JOB_NAME)
        with pytest.raises(AirflowException, match=exception_message):
            run = {"job_id": JOB_ID, "job_name": JOB_NAME}
            DatabricksRunNowOperator(task_id=TASK_ID, json=run)
        with pytest.raises(AirflowException, match=exception_message):
            run = {"job_id": JOB_ID}
            DatabricksRunNowOperator(task_id=TASK_ID, json=run, job_name=JOB_NAME)
    @mock.patch("airflow.providers.databricks.operators.databricks.DatabricksHook")
    def test_exec_with_job_name(self, db_mock_class):