This worked for me, once I upgraded the CLI to v0.287.0. I am using two schemas in the lvdash.json file but only one catalog. What I did was to  only parametrize the catalog name in the yml file,

variables:
  warehouse_id:
    description: SQL Warehouse ID
    default: xxxx
  catalog_name:
    description: Catalog name
    default: dev_gold

resources:
  dashboards:
    dashboard_example:
      display_name: 'Dashboard_Demo'
      file_path: ../../dashboards/my_dashboard.lvdash.json
      warehouse_id: ${var.warehouse_id}
      dataset_catalog: ${var.catalog_name}

targets:
  dev:
    mode: development
    default: true
    workspace:
      host: https://adb-xxx.azuredatabricks.net
    variables:
      catalog_name: dev_gold
      warehouse_id: xxx

   prod:
     mode: production
     workspace:
      host: https://adb-yyy.azuredatabricks.net
    variables:
      catalog_name: gold
      warehouse_id: yyy

and once I deployed, it could pick up the right schema names. In the lvdash.json file, I only omitted the catalog name and left the schema names, as follows:

"queryLines": [
        "SELECT * FROM schema_1.table1"
      ]
...

"queryLines": [
        "SELECT * FROM schema_2.table2"
      ]