[BUG] MV creation issue when using window.start as a paramater.

[ps48]

What is the bug?
Create acceleration flyout fails to create an acceleration when window.start is used as a paramater in the MV aggregations.

How can one reproduce the bug?
Steps to reproduce the behavior:

1. Go to create acceleration flyout
2. Click on create acceleration with MV and add window.start as a paramater
3. Scroll down to see the generated query
4. Click on create acceleration

Work around
Today users have a work around to this, that they can edit in workbench and remove the backticks for window.start command in MV

FROM:
CREATE MATERIALIZED VIEW myglue.default.mv_1
AS SELECT
   count(`@timestamp`) AS `counter1`, 
   `window.start`
FROM myglue.default.reddyvam
GROUP BY TUMBLE (`@timestamp`, '1 minute')
 WITH (
index_settings = '{"number_of_shards":1,"number_of_replicas":1}',
auto_refresh = true,
refresh_interval = '15 minutes',
watermark_delay = '1 minute',
checkpoint_location = 's3://ckpt'
)

TO:
CREATE MATERIALIZED VIEW myglue.default.mv_1
AS SELECT
   count(`@timestamp`) AS `counter1`, 
   window.start
FROM myglue.default.reddyvam
GROUP BY TUMBLE (`@timestamp`, '1 minute')
 WITH (
index_settings = '{"number_of_shards":1,"number_of_replicas":1}',
auto_refresh = true,
refresh_interval = '15 minutes',
watermark_delay = '1 minute',
checkpoint_location = 's3://ckpt'
)

What is the expected behavior?
The expected behavior is that the MV creation succeeds and window.start is quoted properly.

What is your host/environment?

• OS: Linux
• Version: 2.13
• Plugins: dashboards-observability

Do you have any screenshots?

Do you have any additional context?
Add any other context about the problem.