[FrontEnd] wrong calls to structuredFiles endpoint in artifacts of type DB

When creating a DB artifact, following next steps:

• Creating DB connection information with StreamingAPI (FrontEnd has an issue in progress and cannot be used).
• Browsing with the artifact via FrontEnd

The GovernanceAPI returns the following error:

{
    "status": "Bad Request",
    "statusCode": 400,
    "path": "/structuredFiles/ebecf784-c6f3-43a1-9fde-fa3a1cc816f7",
    "message": "Entity with id ebecf784-c6f3-43a1-9fde-fa3a1cc816f7 is not a StructuredDataset",
    "instant": "2024-12-15T09:13:49.550174828Z"
}

This is because the information must be retrieved with the DB endpoints (database, tables, etc.) and not with the "structuredFiles" endpoints. At this point we need to analyse the flow again

Examples: to retrieve tables information:

curl --location 'http://localhost:8091/databases/ebecf784-c6f3-43a1-9fde-fa3a1cc816f7/tables' --header 'Accept: application/json'

To retrieve columns information from one table:

curl --location 'http://localhost:8091/tables/c28476c6-c583-4d53-831d-0b4141a53e3a/columns' --header 'Accept: application/json'

Please, have a look at our first analysis in the Miro board. When working with DB we have two levels: tables & columns.

/cc @anacosta