Superset ingestion fails when Database Service Name is specified in configuration

[razer-oliverq]

Affected module
Superset Lineage with OM Database Service

Describe the bug

Superset metadata ingestion fails when Database Service Name is specified as per the documentation here:
https://docs.open-metadata.org/v1.4.x/connectors/dashboard/superset

To Reproduce

1. Create database service of type Redshift or Postgres and ingest the metadata. In my case the databaseService name is bigdata-lakehouse.
2. Create a dashboard service of type Superset and specify the databaseService name that was created in (1)
3. Run the metadata ingestion for Superset.
4. Superset dashboards, charts, and data models load as expected, including lineage between assets within Superset. But logs show error message regarding databaseService:

Error to yield dashboard lineage details for DB service name [bigdata-lakehouse]: 'Engine' object has no attribute 'fetch_datasource'

Traceback (most recent call last):
  File "/home/airflow/.local/lib/python3.10/site-packages/metadata/ingestion/source/dashboard/superset/mixin.py", line 185, in yield_dashboard_lineage_details
    datasource_json = self.client.fetch_datasource(
AttributeError: 'Engine' object has no attribute 'fetch_datasource'

Expected behavior

Lineage should be generated between the Superset models and the underlying tables in the specified databaseService.

Version:

• OS: Linux 5.10.213-201.855.amzn2.x86_64 on EKS
• OpenMetadata version: 1.4.1
• OpenMetadata Ingestion package version: openmetadata-ingestion==1.4.1.0
• Superset database type: Aurora Postgres 15.4