### Apache Airflow version

2.6.1

### What happened

The type of the libraries field in the DatabricksSubmitRunOperator is incorrect. According to the Databricks docs, the values should look more like:

```python
[
    {"pypi": {"package": "simplejson"}},
    {"pypi": {"package": "Faker"}},
]
```

as opposed to what the type hint implies:

```python
[
    {"pypi": "simplejson"},
    {"pypi":  "Faker"},
]
```

https://github.com/apache/airflow/blob/providers-databricks/4.2.0/airflow/providers/databricks/operators/databricks.py#L306

### What you think should happen instead

_No response_

### How to reproduce

n/a

### Operating System

macOS

### Versions of Apache Airflow Providers

_No response_

### Deployment

Astronomer

### Deployment details

_No response_

### Anything else

_No response_

### Are you willing to submit 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)

of the ``DatabricksRunNowOperator`` directly. Note that there is exactly
    one named parameter for each top level parameter in the ``run-now``
    endpoint. In this method, your code would look like this: ::
        job_id=42
        notebook_params = {
            "dry-run": "true",
            "oldest-time-to-consider": "1457570074236"
        }
        python_params = ["douglas adams", "42"]
        jar_params = ["douglas adams", "42"]
        spark_submit_params = ["--class", "org.apache.spark.examples.SparkPi"]
        notebook_run = DatabricksRunNowOperator(
            job_id=job_id,
            notebook_params=notebook_params,
            python_params=python_params,
            jar_params=jar_params,
            spark_submit_params=spark_submit_params
        )
    In the case where both the json parameter **AND** the named parameters
    are provided, they will be merged together. If there are conflicts during the merge,
    the named parameters will take precedence and override the top level ``json`` keys.
    Currently the named parameters that ``DatabricksRunNowOperator`` supports are
        - ``job_id``
        - ``job_name``
        - ``json``
        - ``notebook_params``
        - ``python_params``
        - ``python_named_parameters``
        - ``jar_params``
        - ``spark_submit_params``