Remove Databricks v1 provider in favor of v2

**What problem would this solve?**
Databricks providers sometimes show both v1 and v2 options confusing users which to choose

**What would a good outcome look like?**
Only Databricks v2 remains

**Possible approaches**
We can remove the databricks v1 provider and implement a shim to route config files which were pointed at databricks to v1 to upgrade the config file provider entry to v2

**Additional context**
N/A

- [x] I have verified this does not duplicate an existing feature request

Do not begin implementation until the issue reaches **Ready** on the [Goose Issues board](https://github.com/orgs/aaif-goose/projects/1).

Find the Databricks v1 provider code and its configuration format. Understand how the v2 provider differs. The shim must detect v1 configs and upgrade them to v2. Look for existing provider removal or migration examples in the codebase. Testing involves ensuring existing configs using v1 are correctly migrated and that only v2 remains available.

索引モデルが issue の本文から書いたものです。