Updated native models may lose their result set metadata

[zbodi74]

Describe the bug

Upon updating a native model which is based on another model, the result set metadata may be lost.
When this occurs, the query editor won't show available columns for questions that are based on this model.

The workaround is to update the model, and making sure to preview the results before saving it.

To Reproduce

1. Create native model model1:

      select 1 as "client_id", 1 as "value"
UNION select 1 as "client_id", 2 as "value"
UNION select 2 as "client_id", 3 as "value"
UNION select 3 as "client_id", 4 as "value"

2. Create and save a native model model2, which uses model1 as its source:

select * from {{ #nnn-model1 }}

3. Update the query definition of model2, and make a minor, non-impactful change, for instance:

select cte.* from {{ #nnn-model1 }} as cte

, and save it, without previewing the results in the editor.

4. Now start a GUI question based on model2.
5. (!)The columns of the model won't be available in the editor.

Expected behavior

It should wirk

Logs

Logs:

2023-12-20 18:47:06,445 INFO api.dataset :: Source query for this query is Card 77
2023-12-20 18:47:06,455 WARN middleware.add-implicit-clauses :: Warning: cannot determine fields for an explicit `source-query` unless you also include `source-metadata`.
Query: {:params [],
 :native
 "select cte.* from (select 1 as \"client_id\", 1 as \"value\"\nUNION select 1 as \"client_id\", 2 as \"value\"\nUNION select 2 as \"client_id\", 3 as \"value\"\nUNION select 3 as \"client_id\", 4 as \"value\") as cte"}

/api/card response for model2:

{
  "description": null,
  "archived": false,
  "collection_position": 1,
  "table_id": null,
  "result_metadata": null,
  "creator": {
[…]
  },
  "can_write": true,
  "database_id": 1,
  "enable_embedding": false,
  "collection_id": null,
  "query_type": "native",
  "name": "model2",
  "last_query_start": "2023-12-20T18:49:08.371778Z",
  "dashboard_count": 0,
  "persisted": false,
  "average_query_time": 21.0,
  "creator_id": 1,
  "moderation_reviews": [],
  "updated_at": "2023-12-20T18:47:06.210264Z",
  "made_public_by_id": null,
  "embedding_params": null,
  "cache_ttl": null,
  "dataset_query": {
    "type": "native",
    "native": {
      "query": "select cte.* from {{ #76-model1 }} as cte",
      "template-tags": {
        "#76-model1": {
          "type": "card",
          "name": "#76-model1",
          "id": "56149603-5eb3-4829-84a3-1afb2774f8ff",
          "card-id": 76,
          "display-name": "#76 Model1"
        }
      }
    },
    "database": 1
  },
  "id": 77,
  "parameter_mappings": [],
  "display": "table",
  "entity_id": "srrDqNwZugt2Ip3tYamZH",
  "collection_preview": true,
  "last-edit-info": {
[…]
  },
  "visualization_settings": {
    "table.pivot_column": "client_id",
    "table.cell_column": "value"
  },
  "collection": {
    "metabase.models.collection.root/is-root?": true,
    "authority_level": null,
    "name": "Our analytics",
    "is_personal": false,
    "id": "root",
    "can_write": true
  },
  "metabase_version": "v1.48.1 (a8302d4)",
  "parameters": [],
  "dataset": true,
  "created_at": "2023-12-20T18:45:50.916686",
  "parameter_usage_count": 0,
  "public_uuid": null
}```

### Information about your Metabase installation

```JSON
1.48.0, 1.47.9

Severity

Found this while troubleshooting for a customer. A simple workaround exists.

Additional context

No response

[kamilmielnik]

Reopening. Fix will be reverted. See Slack discussion.