Timezone naming is incorrect for pipelines schedules cron time.

When creating a new pipeline schedule and searching for timezone the timezone naming is incorrect.

reproducible on gitlab.com

enter some project and choose: CICD -> Schedules
click New schedule
click Cron Timezone dropdown, Timezone chooser will be pulled down.
now focus on the Filter input field and start typing values.
if look for Timezone by city, it's fine: eg. for "Bratislava" the UTC+1 is brought now (during the summer UTC+2 was brought, which is correct). Similar for other cities.
However, if you look for Timezone by its abbreviation and type: "CEST" the wrong Timezone is brought; "UTC+2 Bucharest" which is wrong, Bucharest is EET => Eastern European Timezone, one timezone to the east from CET. If you type CET (non-DST Central European Timezone) then several alternatives are brought, one of them almost right: UTC+1 West Central Africa - so, CET during the winter is UTC+1, but why West Africa, as West Africa Timezone is called WAT.