docs: cut 6.1.0 versions for docs, admin_docs, developer_docs, components

- Snapshot all four versioned docs sections at v6.1.0; master continues to
  serve as "Next" (lastVersion: current, banner: unreleased) so editing
  master keeps updating the canonical URLs
- Enable the previously-disabled components plugin and version it
- Rename stale "developer_portal" references to "developer_docs" across
  package.json scripts, manage-versions.mjs, theme files (DocVersionBadge,
  DocVersionBanner), DOCS_CLAUDE.md, and README.md (URL backward-compat
  redirect /developer_portal/* preserved)
- Add admin_docs version scripts; drop dead "tutorials" plugin id from
  the version badge
- Generalize fixVersionedImports in manage-versions.mjs to walk every
  section's snapshot and rewrite ../../src/ and ../../data/ imports,
  catching admin_docs and components files that previous version cuts
  would have broken
- Remove orphan files: developer_portal_versions.json,
  tutorials_versions.json, and stray empty versions.json files inside
  components/ and developer_docs/ content directories

docs/versioned_docs/version-6.1.0/databases/index.mdx

@@ -0,0 +1,93 @@
+---
+title: Connecting to Databases
+sidebar_label: Overview
+sidebar_position: 1
+---
+
+{/*
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements.  See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership.  The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License.  You may obtain a copy of the License at
+
+  http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied.  See the License for the
+specific language governing permissions and limitations
+under the License.
+*/}
+
+import { DatabaseIndex } from '@site/src/components/databases';
+import databaseData from '@site/src/data/databases.json';
+
+# Connecting to Databases
+
+Superset does not ship bundled with connectivity to databases. The main step in connecting
+Superset to a database is to **install the proper database driver(s)** in your environment.
+
+:::note
+You'll need to install the required packages for the database you want to use as your metadata database
+as well as the packages needed to connect to the databases you want to access through Superset.
+For information about setting up Superset's metadata database, please refer to
+installation documentations ([Docker Compose](/admin-docs/installation/docker-compose), [Kubernetes](/admin-docs/installation/kubernetes))
+:::
+
+## Supported Databases
+
+Superset supports **80 databases** with varying levels of feature support.
+Click on any database name to see detailed documentation including connection strings,
+authentication methods, and configuration options.
+
+<DatabaseIndex data={databaseData} />
+
+## Installing Database Drivers
+
+Superset requires a Python [DB-API database driver](https://peps.python.org/pep-0249/)
+and a [SQLAlchemy dialect](https://docs.sqlalchemy.org/en/20/dialects/) to be installed for
+each database engine you want to connect to.
+
+### Installing Drivers in Docker
+
+For Docker deployments, create a `requirements-local.txt` file in the `docker` directory:
+
+```bash
+# Create the requirements file
+touch ./docker/requirements-local.txt
+
+# Add your driver (e.g., for PostgreSQL)
+echo "psycopg2-binary" >> ./docker/requirements-local.txt
+```
+
+Then restart your containers. The drivers will be installed automatically.
+
+### Installing Drivers with pip
+
+For non-Docker installations:
+
+```bash
+pip install <driver-package>
+```
+
+See individual database pages for the specific driver packages needed.
+
+## Connecting Through the UI
+
+1. Go to **Settings → Data: Database Connections**
+2. Click **+ DATABASE**
+3. Select your database type or enter a SQLAlchemy URI
+4. Click **Test Connection** to verify
+5. Click **Connect** to save
+
+## Contributing
+
+To add or update database documentation, add a `metadata` attribute to your engine spec class in
+`superset/db_engine_specs/`. Documentation is auto-generated from these metadata attributes.
+
+See [METADATA_STATUS.md](https://github.com/apache/superset/blob/master/superset/db_engine_specs/METADATA_STATUS.md)
+for the current status of database documentation and the [README](https://github.com/apache/superset/blob/master/superset/db_engine_specs/README.md) for the metadata schema.